You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
eladb
changed the title
Source code packaging & uploading
Runtime code packaging & deployment
Jun 13, 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.
The text was updated successfully, but these errors were encountered: