search

openalm / Extension-UtilitiesPack

Release Management utility tasks
Other
34 stars 38 forks source link

Tokenizer does not handle encrypted environment variables #21

Closed robpex closed 7 years ago

robpex commented 8 years ago

Tokenizer will not replace matched variables if the value is encrypted.

pascalberger commented 8 years ago

This might be a duplicate of #20

robpex commented 8 years ago

@pascalberger I understood that to be the "Secret" variables Microsoft documents, such as "Build.BuildNumber or BUILD_BUILDNUMBER". This is about the variables where you click the lock to encrypt them. It's possible they're both not working for the same reason though?

pviktor commented 8 years ago

I've fixed this problem and created a pull request. You can check it.

harshil93 commented 8 years ago

Waiting for the new sdk changes to get in.

zsmorris commented 7 years ago

What's the latest word on when this will be fixed? Extension is pretty much useless without it.

harshil93 commented 7 years ago

@robpex @pascalberger @zsmorris

If you pull in the latest source code and package it and use. You should be able to replace secret vars. Make sure you are using the new CoreCLR based agent with version >= 2.104.2

kvarley commented 7 years ago

I hate to pile on here but is there any plan for releasing this? As near as I can tell, the code is already there but its not packaged as the primary task (tokenize-ps3.ps1).

harshil93 commented 7 years ago

Released. See the 0.1.5 version VSIX package at the root of the github repo.

It will be released to the marketplace very soon ( couple of days)

@kvarley @robpex @pascalberger @zsmorris

You will be able to use secret variables only if you are on >2.104.2 agent version.