feat: expose support links as env variables #11697
Merged
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.
Fixes: #11628
This PR is a workaround to enable support links to be passed as env variables. This is an alternative solution to the proposed concept with enumerated vars (
..._0_NAME
,..._1_NAME
), which might be tricky to implement - discover the number of vars, guess the config schema, etc. JSON object seems to be more flexible format for such cases.or
or in
deployment.yaml