I have a values.yaml file that I use in a helm command in my bitbucket pipeline.
I created a custom pipeline that I run manually.
Below are the beginning parts of my pipeline:
Hey Quintonn,
The environment variable will be injected if you have a secured variable that contains this value to obscure it from view.
For example, say you have a secured variable called $TEST with a value of "helloworld", if you then reference helloworld in plaintext in your configuration - it will automatically insert $TEST as a placeholder to prevent this value from being exposed.
Please review your $MY_ADMIN_PASSWORD variable - you can test by deleting it or changing the value to something completely different to see if it is still inserted when you enter "password".
Cheers!
- Ben (Bitbucket Cloud Support)
Hi,
This is indeed the case.
I did notice this, and I thought my pipeline was failing because it was actually putting the $ value into my files, but it seems it's only for log output.
My problem was unrelated to the passwords and I've figured it out already. Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.