az webapp config set WARNING: App settings have been redacted

[rLindorfer]

Describe the bug

Regression: This problem is caused when upgrading az cli from 2.53.0 to 2.53.1.

Description

When using set commands as described below, a warning message is produced which breaks our build pipelines with failOnStandardError set to true in combination with an error exit code.

Related commands

• az webapp config container set
• az webapp config appsettings set
• az webapp config set

Errors

WARNING: App settings have been redacted.

Issue script & Debug output

WARNING: cli.azure.cli.command_modules.appservice.custom: App settings have been redacted. Use az webapp/logicapp/functionapp config appsettings list to view.

Expected behavior

Configs should be set without any warnings, because it's the natural behavior of setting configs.

Environment Summary

azure-cli                         2.53.1

core                              2.53.1
telemetry                          1.1.0

Extensions:
azure-devops                      0.26.0

Dependencies:
msal                            1.24.0b2
azure-mgmt-resource             23.1.0b2

Python location '/opt/az/bin/python3'
Extensions directory '/opt/az/azcliextensions'

Python (Linux) 3.10.10 (main, Oct 24 2023, 06:10:14) [GCC 11.4.0]

[yonzhan]

Thank you for opening this issue, we will look into it.

[g4mb10r]

Since this is regression, I suggest adding a test case for this.

[BeigeBadger]

I ran into this bug today, thanks for raising an issue @rLindorfer! Hopefully it's resolved soon.

[marrim-myob]

we ran into the same bug ,since the agents upgraded to new az cli version

[mheskandari]

we also have the same issue

[BeigeBadger]

An update to my comment above, I got this issue when using the az functionapp config appsettings set command.

cc @yonzhan

[MaxMommersteeg]

Same issue here when running az functionapp config appsettings set.

[rLindorfer]

Yes, it's very easy to reproduce this issue, simply call az functionapp config appsettings set

Our current workaround is to switch back to az cli 2.53.0 with the following task:

- task: Bash@3
  displayName: "Install AZ CLI 2.53.0"
  inputs:
    targetType: 'inline'
    script: |
      pip install azure-cli==2.53.0

[JonSmith-Work]

Still happening in Azure CLI 2.54.0

[jrunestone]

This issue is unfortunately breaking our pipelines as well.

[6heads]

This still exists in 2.55.0.

@yonzhan Any plans on fixing this?

[segunak]

This still exists in 2.55.0.

@yonzhan Any plans on fixing this?

+1. Any word on a fix for this? We're trying out use of --only-show-errors (details here) on all calls to az functionapp function keys set but ~it does not resolve this issue. The error is still thrown even with that flag~.

Update. Using the 64 bit version of Azure CLI 2.55.0 we're able to get past this issue adding the flag --only-show-errors to all az functionapp or az webapp commands.

[ErikMogensen]

The flag --only-show-errors also works for the 32-bit version of Azure CLI 2.55.0 for those commands.

[rLindorfer]

This means, the only solution is to use the --only-show-errors flag?

[rLindorfer]

What if we do not want to use the --only-show-errors flag?

[vishal-narayanan]

any one knows why it changes the value to false while deploying?

[mheskandari]

it happens also in az cli 2.62.0

[jakub-bochenski]

Is azure-cli no longer maintaned?

This warning is printed even with --output none

So you are warning me that you are now not printing the settings that I requested you not to print?

[zorbla]

Still happening with azure-cli 2.64.0. It's setting values, then prints warning and then it outputs json of the just changed settings with all values being "null" (which is wrong).