create-ampless 0.2.0-alpha.10 → 0.2.0-alpha.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/templates/_shared/amplify/auth/post-confirmation/resource.ts +6 -0
- package/dist/templates/_shared/amplify/events/processor-untrusted/resource.ts +4 -0
- package/dist/templates/_shared/amplify/functions/user-admin/resource.ts +6 -0
- package/dist/templates/_shared/app/globals.css +13 -0
- package/dist/templates/_shared/package.json +2 -2
- package/package.json +1 -1
|
@@ -3,4 +3,10 @@ import { defineFunction } from '@aws-amplify/backend'
|
|
|
3
3
|
export const postConfirmation = defineFunction({
|
|
4
4
|
name: 'post-confirmation',
|
|
5
5
|
entry: './handler.ts',
|
|
6
|
+
// Auth trigger — assign to the auth nested stack so CFN doesn't
|
|
7
|
+
// place it in a separate `function` stack that ends up in a
|
|
8
|
+
// circular dependency loop with auth (which references this
|
|
9
|
+
// function) and storage/data (which auth happens to reach via
|
|
10
|
+
// cross-stack refs the function adds).
|
|
11
|
+
resourceGroupName: 'auth',
|
|
6
12
|
})
|
|
@@ -6,4 +6,8 @@ export const processorUntrusted = defineFunction({
|
|
|
6
6
|
// Untrusted plugins do pure JS work; modest memory.
|
|
7
7
|
memoryMB: 256,
|
|
8
8
|
timeoutSeconds: 30,
|
|
9
|
+
// Pin to the data stack so all event-system Lambdas live together
|
|
10
|
+
// (dispatcher / processor-trusted are also `data`) and the function
|
|
11
|
+
// stack doesn't bridge data ↔ storage ↔ auth in a CFN cycle.
|
|
12
|
+
resourceGroupName: 'data',
|
|
9
13
|
})
|
|
@@ -1,6 +1,12 @@
|
|
|
1
1
|
import { defineFunction } from '@aws-amplify/backend'
|
|
2
2
|
|
|
3
|
+
// `resourceGroupName: 'data'` co-locates this Lambda with the AppSync
|
|
4
|
+
// stack. Required because ampless wires userAdmin as a custom GraphQL
|
|
5
|
+
// resolver (data → function) while api-key-renewer reads graphqlApi
|
|
6
|
+
// (function → data); leaving userAdmin in the default `function` stack
|
|
7
|
+
// turns those two arrows into a CloudFormation circular dependency.
|
|
3
8
|
export const userAdmin = defineFunction({
|
|
4
9
|
name: 'user-admin',
|
|
5
10
|
entry: './handler.ts',
|
|
11
|
+
resourceGroupName: 'data',
|
|
6
12
|
})
|
|
@@ -1,4 +1,17 @@
|
|
|
1
1
|
@import 'tailwindcss';
|
|
2
|
+
|
|
3
|
+
/*
|
|
4
|
+
* Tailwind v4 doesn't scan `node_modules/` by default. The admin UI
|
|
5
|
+
* (`@ampless/admin`) and runtime UI bits (`@ampless/runtime`) ship
|
|
6
|
+
* compiled JS that uses Tailwind utility classes; without these
|
|
7
|
+
* explicit sources, every utility used only inside those packages
|
|
8
|
+
* (e.g. the admin sidebar's `flex`, `fixed`, `md:sticky`, ...) gets
|
|
9
|
+
* tree-shaken out of the final CSS, and the admin layout falls back
|
|
10
|
+
* to browser defaults — sidebar overlaps main content, etc.
|
|
11
|
+
*/
|
|
12
|
+
@source '../node_modules/@ampless/admin/dist';
|
|
13
|
+
@source '../node_modules/@ampless/runtime/dist';
|
|
14
|
+
|
|
2
15
|
@plugin '@tailwindcss/typography';
|
|
3
16
|
/* DADS theme plugin from Digital Agency. Loaded globally so the
|
|
4
17
|
* `templates/dads/` theme can use DADS-conformant color variables
|
|
@@ -27,8 +27,8 @@
|
|
|
27
27
|
"@ampless/plugin-rss": "^0.2.0-alpha.3",
|
|
28
28
|
"@ampless/plugin-seo": "^0.2.0-alpha.3",
|
|
29
29
|
"@ampless/plugin-webhook": "^0.2.0-alpha.3",
|
|
30
|
-
"@ampless/admin": "^0.2.0-alpha.
|
|
31
|
-
"@ampless/backend": "^0.2.0-alpha.
|
|
30
|
+
"@ampless/admin": "^0.2.0-alpha.11",
|
|
31
|
+
"@ampless/backend": "^0.2.0-alpha.5",
|
|
32
32
|
"@ampless/runtime": "^0.2.0-alpha.5",
|
|
33
33
|
"@digital-go-jp/tailwind-theme-plugin": "^0.3.4",
|
|
34
34
|
"ampless": "^0.2.0-alpha.3",
|