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

Composability by component #385

Merged
merged 7 commits into from
Mar 14, 2022
Merged

Composability by component #385

merged 7 commits into from
Mar 14, 2022

Conversation

jeff-mccoy
Copy link
Contributor

Closes #384

jeff-mccoy and others added 4 commits March 12, 2022 02:03
To prevent the json schema from breaking with prior versions, making the name key optional still allows custom name mappings, but defaults to just use the same name as the main component.

Also updated the json schema and shortened the name key since we are already pointing to another component.
@jeff-mccoy jeff-mccoy added this to the Zarf GA milestone Mar 12, 2022
@jeff-mccoy jeff-mccoy marked this pull request as ready for review March 12, 2022 21:44
@jeff-mccoy jeff-mccoy mentioned this pull request Mar 12, 2022
@jeff-mccoy jeff-mccoy requested a review from YrrepNoj March 12, 2022 22:01
@jeff-mccoy jeff-mccoy merged commit 597054b into master Mar 14, 2022
@jeff-mccoy jeff-mccoy deleted the composability-by-component branch March 14, 2022 01:48
Noxsios pushed a commit that referenced this pull request Mar 8, 2023
- refactor composing to be component specific
- fixes relative path backtracking when recursively composing components
- add optional name key to prevent breaking backwards compatability
- handle parent component overrides

Co-authored-by: Jon Perry <[email protected]>
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

Successfully merging this pull request may close these issues.

Composability should be a 1:1 match for components
3 participants