Replies: 2 comments
|
Just after posting the question, another variant popped into my mind to try:
This syntax works. (msb team, please update the docs accordingly, thank you!) |
0 replies
|
thanks for raising the issue. yes, we did change this recently. it wasn't reflected yet in the docs because #1116 hadn't been merged yet. the docs should already reflect this new behaviour. thanks! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
After upgrading to msb 0.6.4, I cannot use
--secret SECRET=$ENV_VAR@HOSTanymore. The error message says:So I tried
--secret SECRET=ENV_VAR@HOST(no$) and--secret SECRET=\$ENV_VAR@HOST(escaped$) to try passing the env var's name instead of the content, but both attempts fail with the same error as above.The CLI docs don't shed any light on the expected syntax. How do I specify secrets on the command line in 0.6.4+?
All reactions