Interface StageProps
- All Superinterfaces:
software.amazon.jsii.JsiiSerializable
- All Known Implementing Classes:
StageProps.Jsii$Proxy
Example:
App app;
new Stage(app, "DevStage");
Stage.Builder.create(app, "BetaStage")
.permissionsBoundary(PermissionsBoundary.fromName("beta-permissions-boundary"))
.build();
Stage.Builder.create(app, "GammaStage")
.permissionsBoundary(PermissionsBoundary.fromName("prod-permissions-boundary"))
.build();
Stage.Builder.create(app, "ProdStage")
.permissionsBoundary(PermissionsBoundary.fromName("prod-permissions-boundary"))
.build();
-
Nested Class Summary
Nested ClassesModifier and TypeInterfaceDescriptionstatic final classA builder forStagePropsstatic final classAn implementation forStageProps -
Method Summary
Modifier and TypeMethodDescriptionstatic StageProps.Builderbuilder()default EnvironmentgetEnv()Default AWS environment (account/region) forStacks in thisStage.default StringThe output directory into which to emit synthesized artifacts.default PermissionsBoundaryOptions for applying a permissions boundary to all IAM Roles and Users created within this Stage.default List<IPolicyValidationPluginBeta1>Validation plugins to run during synthesis.default StringName of this stage.Methods inherited from interface software.amazon.jsii.JsiiSerializable
$jsii$toJson
-
Method Details
-
getEnv
Default AWS environment (account/region) forStacks in thisStage.Stacks defined inside this
Stagewith eitherregionoraccountmissing from its env will use the corresponding field given here.If either
regionoraccountis is not configured forStack(either on theStackitself or on the containingStage), the Stack will be environment-agnostic.Environment-agnostic stacks can be deployed to any environment, may not be able to take advantage of all features of the CDK. For example, they will not be able to use environmental context lookups, will not automatically translate Service Principals to the right format based on the environment's AWS partition, and other such enhancements.
Default: - The environments should be configured on the `Stack`s.
Example:
// Use a concrete account and region to deploy this Stage to // Use a concrete account and region to deploy this Stage to Stage.Builder.create(app, "Stage1") .env(Environment.builder().account("123456789012").region("us-east-1").build()) .build(); // Use the CLI's current credentials to determine the target environment // Use the CLI's current credentials to determine the target environment Stage.Builder.create(app, "Stage2") .env(Environment.builder().account(process.getEnv().getCDK_DEFAULT_ACCOUNT()).region(process.getEnv().getCDK_DEFAULT_REGION()).build()) .build(); -
getOutdir
The output directory into which to emit synthesized artifacts.Can only be specified if this stage is the root stage (the app). If this is specified and this stage is nested within another stage, an error will be thrown.
Default: - for nested stages, outdir will be determined as a relative directory to the outdir of the app. For apps, if outdir is not specified, a temporary directory will be created.
-
getPermissionsBoundary
Options for applying a permissions boundary to all IAM Roles and Users created within this Stage.Default: - no permissions boundary is applied
-
getPolicyValidationBeta1
Validation plugins to run during synthesis.If any plugin reports any violation, synthesis will be interrupted and the report displayed to the user.
Default: - no validation plugins are used
-
getStageName
Name of this stage.Default: - Derived from the id.
-
builder
- Returns:
- a
StageProps.BuilderofStageProps
-