search

openalm / Extension-UtilitiesPack

Release Management utility tasks
Other
34 stars 38 forks source link

"Secret" configuration variables are not tokenized #20

Open ivanz opened 8 years ago

ivanz commented 8 years ago

"Secret" configuration variables (in an environment in Release Management in VSTS) are not tokenized.

spoonraker commented 7 years ago

I just downloaded and installed this extension yesterday and it is still not replacing secret variables for me. I just did multiple tests on my release where I changed the variable from secret to not-secret and queued back-to-back releases and watched it fail every time it was marked secret.

I read the other issue linked above and people seem to have stated that if you download the source code yourself it works, but if you install from the marketplace it doesn't. I believe we installed the extension from the marketplace.

I just wanted to reply so this was brought back to somebody's attention. This is a critical feature and it should be available in the marketplace. If the code has been written for months, why not push this change to the marketplace by now?

ukphillips commented 7 years ago

@spoonraker I just had the same issue - according to other threads this should be fixed with version 0.1.5, and I have installed 0.1.6, and it is still not working. Very confused as that looks like the most recent version that is in the repo.

616b2f commented 7 years ago

Same issue here, I am using: Microsoft Visual Studio Team Foundation Server Version 15.112.26307.0

In logs I get "No value found for token '__testpwd__'" for secret variables.

616b2f commented 7 years ago

We resolved this issue by updating the Build Agents to the latest release (v2.x).