Appconfiguration: Azure DevOps Extension: Azure AppConfiguration - Partial Complete

Created on 17 Jul 2020  ·  12Comments  ·  Source: Azure/AppConfiguration

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.
Azure Pipelines enhancement

Most helpful comment

Okay, that's what I'm leaning toward and want to make sure we are all on the same page.

All 12 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 conditions which could let the follow task to continue to ran or canceled based on previous tasks' results.

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.

image

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

Was this page helpful?
0 / 5 - 0 ratings

Related issues

kamalsivalingam picture kamalsivalingam  ·  6Comments

syndicatedshannon picture syndicatedshannon  ·  7Comments

David-Stark picture David-Stark  ·  5Comments

sslepova picture sslepova  ·  4Comments

kamalsivalingam picture kamalsivalingam  ·  3Comments