-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write endpoint username #6471
Comments
@GitHubSriramB for service endpoint question |
@mmajcica - All endpoint authorization parameters are getting masked by the agent. This is same as following issue: microsoft/azure-pipelines-agent#1207 When an endpoint auth. parameter value is masked, the string gets masked even when it gets logged through another variable. This is expected. @bryanmacfarlane - any update on whether the service-side bug in Build is address to remove the agent from masking all endpoint authorization parameters? |
@GitHubSriramB is there a way to bypass this limitation? It is not only applicable to the endpoint values, but also to any variable that has been named UserName or similar. |
@bryanmacfarlane @GitHubSriramB guys any ideas about this? |
@mmajcica - the masking happens only based on value of endpoint authorization parameters. If value of variable named as UserName is different from the values of any of the endpoint authorization parameters, then the variable value should not get masked. |
@mmajcica This is not a tasks bug. To suggest a new feature, please create a new post on the Azure DevOps Developer Community site. Thank you! |
From my custom task I'm trying to output some information. One of it is my endpoint username. The other one is a value from a variable called $Username.
In both cases I do get:
MDS admin is reset to '********'.
Is there a way to overcome this protection?
Thanks
The text was updated successfully, but these errors were encountered: