-
Couldn't load subscription status.
- Fork 284
Open
Labels
kind/enhancementAn entirely new featureAn entirely new featurekind/proposalIndicates maintainers have not yet committed to a feature requestIndicates maintainers have not yet committed to a feature requestneeds/areaIssue or PR needs to be labeled to indicate what parts of the code base are affectedIssue or PR needs to be labeled to indicate what parts of the code base are affectedneeds/priorityPriority has not yet been determined; a good signal that maintainers aren't fully committedPriority has not yet been determined; a good signal that maintainers aren't fully committed
Description
Checklist
- I've searched the issue queue to verify this is not a duplicate feature request.
- I've pasted the output of
kargo version, if applicable. - I've pasted logs, if applicable.
Proposed Feature
yaml-update promotion step is now (v1.8.0) able to update keys that are present in yaml document, but cannot create a new ones, when they are missing.
Motivation
I would like to be able to include metadata from promotion like freight name in the yaml document even though the yaml doesn't contain prepared placeholder for it (thus reducing some boilerplate, when configuring source yaml document first time).
dt-teck
Metadata
Metadata
Assignees
Labels
kind/enhancementAn entirely new featureAn entirely new featurekind/proposalIndicates maintainers have not yet committed to a feature requestIndicates maintainers have not yet committed to a feature requestneeds/areaIssue or PR needs to be labeled to indicate what parts of the code base are affectedIssue or PR needs to be labeled to indicate what parts of the code base are affectedneeds/priorityPriority has not yet been determined; a good signal that maintainers aren't fully committedPriority has not yet been determined; a good signal that maintainers aren't fully committed