Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One-click deployment CloudFormation template support #7860

Open
2 tasks
zxkane opened this issue May 8, 2020 · 1 comment
Open
2 tasks

One-click deployment CloudFormation template support #7860

zxkane opened this issue May 8, 2020 · 1 comment
Labels
@aws-cdk/core Related to core CDK functionality effort/medium Medium work item – several days of effort feature-request A feature should be added or improved. p2 package/tools Related to AWS CDK Tools or CLI

Comments

@zxkane
Copy link
Contributor

zxkane commented May 8, 2020

I want to publish CDK application to CloudFormation template with assets to S3 with one-click deployment enabled.

Use Case

There still are some barriers for end users to apply/evaluate a CDK based solution(installing prerequisites tools, cloning AWS solution source, installing dependencies, configuring aws credential, finally deploying cdk application).

One-click deployment CloudFormation template would simplify the user experiences.

Currently the synthesized output CFN template is using CfnParameter for external assets that will be specified in deployment runtime. It's very difficult to fill those parameters properly with the assets information in a manual publishing.

Proposed Solution

I think the most of work already done in cdk deploy command, it always uploads assets and templates to cdk staging bucket, then create cloudformation stack with parameter values of assets from previous step.

The cdk tool impments a new command publish to publish the assets to S3 bucket then updated template with default values for asset parameters and publishing it to S3 bucket as well.

The publish command can specify s3 bucket with prefix for publishing the artifacts or use the cdk-staging-bucket as default bucket.

Other

  • 👋 I may be able to implement this feature request
  • ⚠️ This feature might incur a breaking change

This is a 🚀 Feature Request

@zxkane zxkane added feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged. labels May 8, 2020
@SomayaB SomayaB added @aws-cdk/core Related to core CDK functionality package/tools Related to AWS CDK Tools or CLI labels May 12, 2020
@shivlaks shivlaks added p2 effort/medium Medium work item – several days of effort labels Aug 14, 2020
@SomayaB SomayaB removed the needs-triage This issue or PR still needs to be triaged. label Nov 6, 2020
@NGL321 NGL321 assigned rix0rrr and unassigned shivlaks Jan 25, 2021
@bollig
Copy link

bollig commented Feb 1, 2021

+1 , but make sure the published CFN template abstracts/hides the Asset cloudformation parameter strings. Nothing more confusing than trying to populate Assets parameters manually (defaults don't populate automatically in all contexts) or explaining to an end-user that Asset parameters fields do not need to be modified. At the very least, moving AssetParameters to a separate parameter group would help.

@rix0rrr rix0rrr removed their assignment Jun 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/core Related to core CDK functionality effort/medium Medium work item – several days of effort feature-request A feature should be added or improved. p2 package/tools Related to AWS CDK Tools or CLI
Projects
None yet
Development

No branches or pull requests

5 participants