-
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
Azure DevOps Extension: Azure AppConfiguration - Partial Complete #372
Comments
@Yiming-Jia, not sure if there is a standard way in ADO to suppress warnings. |
Hello @jkrusic19 , Yes, that should be a feature request to the Azure DevOps Pipeline. We use the pipeline task SDK to dump the message with warning log level and mark the task success with issues as the existing key-values overwritten, which is the way the task to notify user. And from Azure DevOps pipeline document, I saw it support the |
Reopen this issue as overwritten is expected in the configuration composition scenario and the warnings are annoying (false alarm). |
imo this a bug and not a feature. |
I agree this is a bug, there are other tasks which can "succeed" fully i.e. be green while supporting a warning in the task i.e. the Kubectl and Terraform tasks - there are warnings in the log, but the task completes successfully - this is the behaviour i would expect from the app configuration task. |
@jkrusic19 I'd like to clarify the original ask a little. We do two things currently when we encounter overwritten keys. We write a warning and we set the pipeline's final state to "succeeded with issues" instead of "succeeded". Is your request for us only to set the final state to "succeeded" rather than "succeeded with issues" or is it to omit the warning messages as well? |
For my 2 cents it should set the final state to “succeeded” and the warning messages should be retained (like in my screenshot from the official Terraform extension) |
Okay, that's what I'm leaning toward and want to make sure we are all on the same page. |
Hello, Yes success with warnings in the log output. |
Came here to make the same case, +1 for success with warnings in the log output |
A new release is out for the Azure App configuration -version 3.2.15, this issue has been addressed in the new release, the final state is set to "succeeded" and the warning messages are retained. In case you experience any issues please reach out. :) |
I have tested and it works like a charm - thanks! |
Hello,
I would like to submit a feature request for the Azure DevOps extension "Azure AppConfiguration". When finding "keys that already exist, and we are going to overwrite" can we have the ability to suppress that warning so our pipelines look all "Green"?
Expected behavior:
The text was updated successfully, but these errors were encountered: