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

Runtime code packaging & deployment #85

Closed
rix0rrr opened this issue Jun 11, 2018 · 0 comments
Closed

Runtime code packaging & deployment #85

rix0rrr opened this issue Jun 11, 2018 · 0 comments
Assignees

Comments

@rix0rrr
Copy link
Contributor

rix0rrr commented Jun 11, 2018

Vision

When I consume a library in my CDK project which contains runtime code, my workflow looks exactly like it looks today. This means that when cdk deploy my application, the runtime code will be automatically and transparently bundled and deployed.

When I write CDK libraries/apps, I can naturally add runtime code to it and CDK constructs can be used to reference it for execution on various compute platforms. Also, referencing CDK values from runtime code should be as strongly-typed and compile-time enforced as possible. This might mean that CDK will generate code.

Thoughts on Design and Staging

There's probably some plugin architecture behind this that allows us to build adapters for various compute platforms and various programming languages (when it comes to bundling). We should look into how existing solutions (e.g. SAM, Serverless, Terraform, Pulumi) approach this problem.
A number of resources require build & upload of source local to the CDK repo.

@eladb eladb changed the title Source code packaging & uploading Runtime code packaging & deployment Jun 13, 2018
@rix0rrr rix0rrr added the design label Jun 22, 2018
@eladb eladb mentioned this issue Jul 18, 2018
@eladb eladb self-assigned this Aug 27, 2019
@eladb eladb closed this as completed Oct 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants