Tokenizer does not handle encrypted environment variables about extension-utilitiespack HOT 8 CLOSED

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

from extension-utilitiespack.

This might be a duplicate of #20

from extension-utilitiespack.

@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?

from extension-utilitiespack.

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

from extension-utilitiespack.

Waiting for the new sdk changes to get in.

from extension-utilitiespack.

@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

from extension-utilitiespack.

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).

from extension-utilitiespack.

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.

from extension-utilitiespack.