-
Notifications
You must be signed in to change notification settings - Fork 15
/
Copy pathamplify-exported-backend-props.ts
36 lines (33 loc) · 1.35 KB
/
amplify-exported-backend-props.ts
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
import { StackProps } from 'aws-cdk-lib';
export interface AmplifyExportedBackendProps extends StackProps {
/**
* The path to the exported folder that contains the artifacts for the Amplify CLI backend
* ex: ./amplify-synth-out/
*/
readonly path: string;
/**
* The Amplify App ID to which the new backend environment will be added.
*
* If the Amplify environment is created and managed by CDK exclusively
* then provide an AmplifyAppId to ensure the backend environment
* shows up in the AWS Amplify App homepage.
*
* If the Amplify environment is created via Amplify CLI, do not
* provide an AmplifyAppId. Trying to create an Amplify backend
* via CDK which has already been created by the Amplify CLI will result
* in the CDK failing to create the backend and automatically deleting
* the existing backend when it deletes the Amplify environment it failed
* to deploy.
*/
readonly amplifyAppId?: string
/**
* An environment name to contain Amplify CLI backend resources.
*
* An Amplify backend is a collection of various AWS
* resources organized into categories (api, function, custom, etc) which are deployed
* together into an environment. Environments sometimes reflect deployment
* stages such as 'dev', 'test', and 'prod'.
* @default is 'dev'
*/
readonly amplifyEnvironment?: string;
}