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

CDK Code Generation from AWS Console #65

Closed
2 tasks
PaulMaddox opened this issue Nov 10, 2019 · 4 comments
Closed
2 tasks

CDK Code Generation from AWS Console #65

PaulMaddox opened this issue Nov 10, 2019 · 4 comments
Labels
effort/large Significant effort required for implementation status/stale The RFC did not get any significant enough progress or tracking and has become stale.

Comments

@PaulMaddox
Copy link

We should integrate the AWS CDK into the console / getting started experience for every AWS service.

#thinkbig

Use Case

As an AWS user, I want to be able to explore and play around with a new service via the AWS Management Console, but then quickly transition to infrastructure as/in code.

Proposed Solution

  • Customer browses to a service console in their browser and creates a resource via a getting started wizard

  • On the final screen there are a couple of new buttons: Create with AWS CDK, and Create with AWS CDK (pipeline).

  • Create with AWS CDK will automatically generate a CDK project, and offer it as a ZIP that can be downloaded. The project will contain a single construct that is being deployed, with the configuration parameters the customer set during the wizard. The UI will show a helpful Getting started with the CDK tutorial to walk them through deploying it.

  • Create with AWS CDK (pipeline) will do the same as above, but automatically check the CDK project into a CodeCommit or GitHub repository, and setup AWS CodePipeline to automatically test and deploy the project.

This assumes that we have constructs/patterns that match our first experience management console wizards.

This functionality should be bundled up, and provided as a self-service library for AWS service owners to easily integrate into their consoles to maximize adoption.

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

This is a 🚀 Feature Request

@rix0rrr
Copy link
Contributor

rix0rrr commented Dec 2, 2019

I've been thinking about this as well. In my head, it was a graphical "construct builder" with copy/pasteable snippets on the right, rather than a downloadable project. No reason why we couldn't have both, I suppose.

image

@eladb
Copy link
Contributor

eladb commented Jan 22, 2020

Transferring this to the RFC repo. Please consult the README file for the RFC repo for instructions on how to propose this feature.

@eladb eladb transferred this issue from aws/aws-cdk Jan 22, 2020
@eladb eladb unassigned eladb Jan 22, 2020
@eladb eladb added the effort/large Significant effort required for implementation label Jan 22, 2020
@eladb eladb added the status/proposed Newly proposed RFC label Jun 23, 2020
@eladb eladb changed the title AWS CDK in the Management Console CDK Code Generation from AWS Console Jun 23, 2020
@luchees
Copy link

luchees commented Aug 25, 2021

Some time ago I found this repo which does something similar: https://github.com/iann0036/AWSConsoleRecorder
Might be interesting to see how they coped with it.

@mrgrain
Copy link
Contributor

mrgrain commented Oct 27, 2023

Marking this RFCs as stale since there has been little recent activity and it is not currently close to getting accepted as-is. We appreciate the effort that has gone into this proposal. Marking an RFCs as stale is not a one-way door. If you have made substantial changes to the proposal, please open a new issue/RFC. You might also consider raising a PR to aws/aws-cdk directly or self-publishing to Construct Hub.

@mrgrain mrgrain closed this as not planned Won't fix, can't repro, duplicate, stale Oct 27, 2023
@mrgrain mrgrain added status/stale The RFC did not get any significant enough progress or tracking and has become stale. and removed status/proposed Newly proposed RFC labels Oct 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/large Significant effort required for implementation status/stale The RFC did not get any significant enough progress or tracking and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants