Hi guys, i am struggling with implementation of a windows private runner for deployment of azure resources.
The runner is configured per the bitbucket documentation and the pipeline connects to it fine.
I have 3 environment variables that I use to connect to azure via cli:
Hey @Nathan Zipf ,
and welcome to the Community!
In order to protect the value of Secure variables from being shown in the logs, Pipelines automatically masks secure variable values from the logs:
If a value matching a secured variable appears in the logs, Pipelines will replace it with $VARIABLE_NAME.
Reference: Secured-variable-masking
This would explain why when you tried to print the secure variable value, it just printed the variable name instead. This does not mean the variable is empty, it's just the masking pipeline is executing to hide the actual value from the logs.
The issue in this case might be the token is not valid, or if you copy/pasted the value into the variable, it may contain a trailing/leading space that is making it invalid.
As you mentioned using a test token to confirm if the value is correct and if it's being passed to the pipeline, I would create that same variable again without using the Secure option and then print it in the logs.
You can then check if the value is correct and if the azure commands succeeds. Once that is confirmed, you can rotate your token and create a new secure variable with the new value.
I hope that information helps! Let us know in case you have any questions.
Thank you, @Nathan Zipf !
Patrik S
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.