Allow stage convention to be selective in its packages to extract#1911
Closed
Allow stage convention to be selective in its packages to extract#1911
Conversation
rain-on
changed the title
Contributor
Author
|
This has been worked around in the new_commit_to_git branch - whereby all packages are unpacked in a flat directory structure then variables are substituted either sensitively/nopnsensitively based on if the package appears in the metadata property |
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
1 participant
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.
The upcoming CommitToGitStep treats the packages in the step as 2 separate lists:
As such, the StageDependencyConvention needs to be updated to be able to selectively extract packages based on arbitrary logic (not defined here).
This change results in no functional changes.