jenkinsci
/
configuration-as-code-plugin
mirror of https://github.com/jenkinsci/configuration-as-code-plugin.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Added escape for secrets to docs (#735) 

Per #697 proper interpolation was added. However, some plugins such as the kubernetes plugin require ${computer.jnlpmac} and ${computer.name} literals in the config.xml. The PR didn't add this extra bit of info for escaping the secrets and would require someone to review the PR to see the escape character of `^`.
This commit is contained in:
Matt L 2019-02-09 02:41:59 -05:00 committed by Ewelina Wilkosz
parent f857cab417
commit de15b8be57
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -207,7 +207,7 @@ with your favourite yaml tools.
Currently, you can provide initial secrets to Configuration-as-Code that all rely on <key,value>
substitution of strings in configuration. For example, ``Jenkins: `${some_var}` ``. Default variable substitution
using the `:-` operator from `bash` is also available. For example, `key: ${VALUE:-defaultvalue}` will evaluate to `defaultvalue` if `$VALUE` is unset.
using the `:-` operator from `bash` is also available. For example, `key: ${VALUE:-defaultvalue}` will evaluate to `defaultvalue` if `$VALUE` is unset. To escape a string from secret interpolation, put `^` in front of the value. For example, `Jenkins: ^${some_var}` will produce the literal `Jenkins: ${some_var}`.
We can provide these initial secrets in the following ways: