-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Document behaviour of script field when "$$" and "$(X)" are used #3939
Conversation
/hold This shouldn't be merged until after the |
There are some nuances and slightly confusing behaviour present in the way our `script` field works. These relate to the way Kubernetes processes the `args` field of containers in order to replace variable references of form `$(X)`. This commit documents the way Kubernetes' variable reference code can mangle the contents of Tekton's `script` blocks.
/hold cancel #3938 has been merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @sbwsg!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerop The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold We won't need this if #3963 goes in instead. |
I'm closing this on the assumption that #3963 is probably the better way forward. |
Changes
There are some nuances and slightly confusing behaviour present in
the way our
script
field works. These relate to the way Kubernetesprocesses the
args
field of containers in order to replace variablereferences of form
$(X)
.This commit documents the way Kubernetes' variable reference code
can mangle the contents of Tekton's
script
blocks.Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
Release Notes