allow template labels to be parameterised#16605
allow template labels to be parameterised#16605openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
|
@bparees it just occurred to me, as this stands, this will allow label /values/ to be parameterised, but not label keys (or ${{json}}) - do you think either of these is warranted? |
fc800a5 to
107ca81
Compare
allowing label keys to be parameterized is warranted imho. Supporting ${{}} syntax is not needed since label keys+values can only be strings anyway(right?) |
107ca81 to
6fd1097
Compare
|
/retest |
1 similar comment
|
/retest |
|
this will need a docs follow up too. |
|
@bparees docs updated |
|
lgtm but holding for 3.8 since we are past feature cut on 3.7. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees, jim-minter The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
|
/test all [submit-queue is verifying that this PR is safe to merge] |
|
@jim-minter: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
Automatic merge from submit-queue (batch tested with PRs 16605, 17270). |
fixes #16223
docs: openshift/openshift-docs#5401