Repository navigation
Azure DevOps Extension: Azure AppConfiguration - Partial Complete #372
Description
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:
- With this specific step, this is expected behavior and do not see it as an issue.
Activity
zhenlan commentedon Jul 17, 2020
yijia (@Yiming-Jia), not sure if there is a standard way in ADO to suppress warnings.
Yiming-Jia commentedon Jul 27, 2020
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
conditionswhich could let the follow task to continue to ran or canceled based on previous tasks' results.zhenlan commentedon Sep 3, 2020
Reopen this issue as overwritten is expected in the configuration composition scenario and the warnings are annoying (false alarm).
mieel commentedon Oct 12, 2020
imo this a bug and not a feature.
TheHodge1234 commentedon Oct 29, 2020
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.
jimmyca15 commentedon Nov 20, 2020
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?
TheHodge1234 commentedon Nov 20, 2020
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)
jimmyca15 commentedon Nov 20, 2020
Okay, that's what I'm leaning toward and want to make sure we are all on the same page.
jkrusic19 commentedon Nov 20, 2020
Hello,
Yes success with warnings in the log output.
crsbrns commentedon Dec 2, 2020
Came here to make the same case, +1 for success with warnings in the log output
MaryanneNjeri commentedon Dec 10, 2020
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. :)
TheHodge1234 commentedon Dec 10, 2020
I have tested and it works like a charm - thanks!