feat(lib): Initial Asset Pipeline implementation#339
Open
eduardomourar wants to merge 4 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issue
Fully Resolves:
Partially Addresses:
Description
Implements a simplified asset staging and bundling pipeline for CDKTN, following patterns from AWS CDK and TerraConstructs while avoiding unnecessary dependencies.
✅ Implemented Features
Core Asset Staging
SOURCE- based on source content (default)OUTPUT- based on bundled outputCUSTOM- user-provided hash.zip,.tar,.tar.gz,.tgzfilesDocker Bundling
ILocalBundlinginterfaceARCHIVED- single archive fileNOT_ARCHIVED- directory of filesSINGLE_FILE- single non-archive fileAUTO_DISCOVER- automatic detectionTest Coverage
⏸️ Intentionally Deferred
To maintain simplicity and avoid new dependencies.
Not Implemented from AWS CDK/TerraConstructs:
esbuilddependencyRationale: These features add significant complexity and external dependencies that aren't needed for the initial use case. The current implementation provides all core functionality (staging, hashing, bundling) with extensible interfaces for future enhancements.
Checklist