|admin||Whether to grant admin permissions to CloudFormation while deploying this template.|
|input||The CodePipeline artifact that holds the synthesized app, which is the contents of the |
|stack||The CDK stack to be deployed.|
|capabilities?||Acknowledge certain changes made as part of deployment.|
|change||The name to use when creating a ChangeSet for the stack.|
|create||The runOrder for the CodePipeline action creating the ChangeSet.|
|execute||The runOrder for the CodePipeline action executing the ChangeSet.|
|role?||IAM role to assume when deploying changes.|
Whether to grant admin permissions to CloudFormation while deploying this template.
Setting this to
true affects the defaults for
capabilities, if you
don't specify any alternatives.
The default role that will be created for you will have admin (i.e.,
permissions on all resources, and the deployment will have named IAM
capabilities (i.e., able to create all IAM resources).
This is a shorthand that you can use if you fully trust the templates that
are deployed in this pipeline. If you want more fine-grained permissions,
capabilities to control what the CloudFormation
deployment is allowed to do.
The CodePipeline artifact that holds the synthesized app, which is the contents of the
<directory> when running
cdk synth -o <directory>.
The CDK stack to be deployed.
(optional, default: [AnonymousIAM, AutoExpand], unless
adminPermissions is true)
Acknowledge certain changes made as part of deployment.
For stacks that contain certain resources, explicit acknowledgement that AWS CloudFormation might create or update those resources. For example, you must specify AnonymousIAM if your stack template contains AWS Identity and Access Management (IAM) resources. For more information
(optional, default: CDK-CodePipeline-ChangeSet)
The name to use when creating a ChangeSet for the stack.
(optional, default: 1)
The runOrder for the CodePipeline action creating the ChangeSet.
createChangeSetRunOrder + 1)
The runOrder for the CodePipeline action executing the ChangeSet.
(optional, default: A fresh role with admin or no permissions (depending on the value of
IAM role to assume when deploying changes.
If not specified, a fresh role is created. The role is created with zero
adminPermissions is true, in which case the role will have