We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is this intentional behavior or a bug?
Currently environment variables are eligible for shell parameter expansion. For example, this task gives string "xxxyyy":
task: - name: prints xxxyyy script: printenv FOO env: {BAR: yyy, FOO: xxx$BAR}
this one gives string "qwe":
task: - name: prints qwe script: printenv PASSWORD env: {PASSWORD: qwe$rty}
commands are also supported:
task: - name: prints xxx script: printenv FOO env: {FOO: $(echo xxx)}
Golang's %q encoding may produce unexpected behavior. This task escapes new line character:
task: - name: prints a\nb (new line is escaped) script: printenv FOO env: {FOO: "a\nb"}
this one escapes part of the emoji:
task: - name: prints 👨\u200d🦰 script: printenv FOO env: {FOO: 👨🦰}
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is this intentional behavior or a bug?
Currently environment variables are eligible for shell parameter expansion. For example, this task gives string "xxxyyy":
this one gives string "qwe":
commands are also supported:
Golang's %q encoding may produce unexpected behavior. This task escapes new line character:
this one escapes part of the emoji:
The text was updated successfully, but these errors were encountered: