-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat(cdk-assets): add external asset support #12259
Conversation
9213a1c
to
b8a7047
Compare
@CaerusKaru this is interesting. Have you discussed this with anyone from the CDK team before submitting? I suspect we may want a quick RFC to better understand the use case behind this and see if this is indeed the best approach. |
packages/@aws-cdk/cloud-assembly-schema/lib/assets/docker-image-asset.ts
Outdated
Show resolved
Hide resolved
packages/@aws-cdk/core/lib/stack-synthesizers/bootstrapless-synthesizer.ts
Outdated
Show resolved
Hide resolved
In the event that assets are not actually available at synthesis time, we still want to support JIT (just-in-time) asset generation via external tooling. This would, for instance, enable a third party tool to fetch additional resources prior to bundling/building and subsequent uploading. This adds a new interface for both File and Docker asset types that allows users to specify an executable. The executable, depending on the asset type, must then reply with a specific key on stdout, which will then get picked up and used by CDK Assets. This also updates the default stack synthesizer to support adding external sources directly. This is technically a breaking change for anyone who currently extends the class.
packages/@aws-cdk/cloud-assembly-schema/schema/cloud-assembly.version.json
Outdated
Show resolved
Hide resolved
packages/@aws-cdk/core/lib/stack-synthesizers/stack-synthesizer.ts
Outdated
Show resolved
Hide resolved
packages/@aws-cdk/core/lib/stack-synthesizers/stack-synthesizer.ts
Outdated
Show resolved
Hide resolved
packages/@aws-cdk/core/lib/stack-synthesizers/stack-synthesizer.ts
Outdated
Show resolved
Hide resolved
packages/@aws-cdk/core/lib/stack-synthesizers/default-synthesizer.ts
Outdated
Show resolved
Hide resolved
packages/cdk-assets/lib/private/handlers/external-container-images.ts
Outdated
Show resolved
Hide resolved
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
@Mergifyio update |
@CaerusKaru is not allowed to run commands |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
In the event that assets are not actually available at synthesis
time, we still want to support JIT (just-in-time) asset
generation via external tooling. This would, for instance, enable
a third party tool to fetch additional resources prior to
bundling/building and subsequent uploading.
This adds a new interface for both File and Docker asset types
that allows users to specify an executable. The executable,
depending on the asset type, must then reply with a specific key
on stdout, which will then get picked up and used by CDK Assets.
This also updates the default stack synthesizer to support adding
external sources directly. This is technically a breaking change
for anyone who currently extends the class.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license