-
Notifications
You must be signed in to change notification settings - Fork 73
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
Value being pulled into Azure DevOps is incorrect #313
Comments
Hello @ssulei7 , Thank you for reporting this issue. After testing, I confirmed this bug, and this is actually a bug from the AzureDevOps pipeline library we're consuming, which is a open source library provided by Azure DevOps team. We already created an issue under this repo: microsoft/azure-pipelines-task-lib#627. You could also check the progress of the fix. We will also keep you updated once they provide us an ETA for the fix. Thank you, |
Thank you for the quick response! |
@Yiming-Jia Hi, following up on this bug to see if there's a working solution in flight? |
Hello @ssulei7 , Sorry for the delay response. We had internal communications with the pipeline library team to narrow down the issue. As they mentioned it's a 'by-design' from their library, we're preparing a change to take off the dependency from our task, which should fix the issue |
Hello @ssulei7 , We just deployed the latest pipeline task to fix this issue. To adjust this change, you have to go to your pipeline task, and select |
I will close this issue. And feel free to contact me if you still have the same issue. |
Hello,
We have a use case within our organization where we are storing credentials within our app configuration service. We are currently running into an issue when we invoke the Azure App Config task where the password we are pulling down does not reflect what is out there in Azure.
Example Password:
myPassWord%
Where the
%
at the end of my password turns into%25
This is currently blocking deployments in our lower environments, so I'm hoping there can be a work around to resolve this issue?
The text was updated successfully, but these errors were encountered: