Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Set-VstsTaskVariable Writes Secret Variable Value to Log

See original GitHub issue

When using the following code in my custom task, the value of the Secret variable is written to the logs. Set-VstsTaskVariable -Name test_pass -Value <password> -Secret;

The output is as follows: ##vso[task.setvariable variable=test_pass;issecret=True]<password>

I would expect the output to be something like this ##vso[task.setvariable variable=test_pass;issecret=True]

This might only happen when using the documentation instructions for Testing and Debugging, I have not tested on our live production system. (https://github.com/Microsoft/vsts-task-lib/blob/master/powershell/Docs/TestingAndDebugging.md)

Issue Analytics

State:
Created 7 years ago
Comments:7 (2 by maintainers)

Top GitHub Comments

2reactions

jtpettycommented, Jan 2, 2020

@damccorm - This was fixed in https://github.com/microsoft/azure-pipelines-agent/pull/2659 of the agent and will be included in 2.164.0

0reactions

damccormcommented, Jan 2, 2020

This is probably related to https://github.com/microsoft/azure-pipelines-task-lib/issues/589 which I believe @jtpetty was taking a look at. Because of our escaping rules, this variable is getting modified as of #543. @jtpetty we should probably react on the agent side and just be a little more aggressive in what we mask.