{AppConfig} Update default connection string resolution logic

[albertofori]

Related command az appconfig

Description

This update ensures that command line arguments take precedence over defaults configured using az configure or in environment variables to avoid conflicts possible conflict errors.

Testing Guide

History Notes

{AppConfig} az appconfig: Update default connection string resolution logic

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• [x] The PR title and description has followed the guideline in Submitting Pull Requests.

• [x] I adhere to the Command Guidelines.

• [x] I adhere to the Error Handling Guidelines.

[yonzhan]

AppConfig

[albertofori]

Hi @avanigupta , could you please take a look at this?

[avanigupta]

@albertofori, we have similar defaults for store name, endpoint and auth-mode (there might be others I'm missing). Can you help to add the same behavior across all our default arguments?

[albertofori]

@albertofori, we have similar defaults for store name, endpoint and auth-mode (there might be others I'm missing). Can you help to add the same behavior across all our default arguments?

Hi @avanigupta, it appears the values that have defaults are automatically handled in the preferred way, however, this issue arose with connection strings due to the dependency between the connection-string and name arguments.

[avanigupta]

This might be a breaking change for some users so please make sure it appears in the release notes.

[zhoxing-ms]

[AppConfig] BREAKING CHANGE: az appconfig: Update default connection string resolution logic

@albertofori In order to reduce the impact of breaking change on users, we usually recommend that breaking change be placed in the breaking change window (twice a year, the date of the next window is in Build Sprint, about May) For more information about the process of breaking change, please refer to document breaking_changes_doc

So I'd like to confirm with you whether we can avoid this breaking change before the next breaking change window?

[albertofori]

[AppConfig] BREAKING CHANGE: az appconfig: Update default connection string resolution logic

@albertofori In order to reduce the impact of breaking change on users, we usually recommend that breaking change be placed in the breaking change window (twice a year, the date of the next window is in Build Sprint, about May) For more information about the process of breaking change, please refer to document breaking_changes_doc

So I'd like to confirm with you whether we can avoid this breaking change before the next breaking change window?

@zhoxing-ms Yes please. I believe we could add this in the next breaking change window. Thanks!

[azure-client-tools-bot-prd[bot]]

️✔️AzureCLI-FullTest

️✔️acr

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️acs

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️advisor

️✔️latest

️✔️3.10

️✔️3.9

️✔️ams

️✔️latest

️✔️3.10

️✔️3.9

️✔️apim

️✔️latest

️✔️3.10

️✔️3.9

️✔️appconfig

️✔️latest

️✔️3.10

️✔️3.9

️✔️appservice

️✔️latest

️✔️3.10

️✔️3.9

️✔️aro

️✔️latest

️✔️3.10

️✔️3.9

️✔️backup

️✔️latest

️✔️3.10

️✔️3.9

️✔️batch

️✔️latest

️✔️3.10

️✔️3.9

️✔️batchai

️✔️latest

️✔️3.10

️✔️3.9

️✔️billing

️✔️latest

️✔️3.10

️✔️3.9

️✔️botservice

️✔️latest

️✔️3.10

️✔️3.9

️✔️cdn

️✔️latest

️✔️3.10

️✔️3.9

️✔️cloud

️✔️latest

️✔️3.10

️✔️3.9

️✔️cognitiveservices

️✔️latest

️✔️3.10

️✔️3.9

️✔️config

️✔️latest

️✔️3.10

️✔️3.9

️✔️configure

️✔️latest

️✔️3.10

️✔️3.9

️✔️consumption

️✔️latest

️✔️3.10

️✔️3.9

️✔️container

️✔️latest

️✔️3.10

️✔️3.9

️✔️core

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️cosmosdb

️✔️latest

️✔️3.10

️✔️3.9

️✔️databoxedge

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️dla

️✔️latest

️✔️3.10

️✔️3.9

️✔️dls

️✔️latest

️✔️3.10

️✔️3.9

️✔️dms

️✔️latest

️✔️3.10

️✔️3.9

️✔️eventgrid

️✔️latest

️✔️3.10

️✔️3.9

️✔️eventhubs

️✔️latest

️✔️3.10

️✔️3.9

️✔️feedback

️✔️latest

️✔️3.10

️✔️3.9

️✔️find

️✔️latest

️✔️3.10

️✔️3.9

️✔️hdinsight

️✔️latest

️✔️3.10

️✔️3.9

️✔️identity

️✔️latest

️✔️3.10

️✔️3.9

️✔️iot

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️keyvault

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️kusto

️✔️latest

️✔️3.10

️✔️3.9

️✔️lab

️✔️latest

️✔️3.10

️✔️3.9

️✔️managedservices

️✔️latest

️✔️3.10

️✔️3.9

️✔️maps

️✔️latest

️✔️3.10

️✔️3.9

️✔️marketplaceordering

️✔️latest

️✔️3.10

️✔️3.9

️✔️monitor

️✔️latest

️✔️3.10

️✔️3.9

️✔️netappfiles

️✔️latest

️✔️3.10

️✔️3.9

️✔️network

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️policyinsights

️✔️latest

️✔️3.10

️✔️3.9

️✔️privatedns

️✔️latest

️✔️3.10

️✔️3.9

️✔️profile

️✔️latest

️✔️3.10

️✔️3.9

️✔️rdbms

️✔️latest

️✔️3.10

️✔️3.9

️✔️redis

️✔️latest

️✔️3.10

️✔️3.9

️✔️relay

️✔️latest

️✔️3.10

️✔️3.9

️✔️resource

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️role

️✔️latest

️✔️3.10

️✔️3.9

️✔️search

️✔️latest

️✔️3.10

️✔️3.9

️✔️security

️✔️latest

️✔️3.10

️✔️3.9

️✔️servicebus

️✔️latest

️✔️3.10

️✔️3.9

️✔️serviceconnector

️✔️latest

️✔️3.10

️✔️3.9

️✔️servicefabric

️✔️latest

️✔️3.10

️✔️3.9

️✔️signalr

️✔️latest

️✔️3.10

️✔️3.9

️✔️sql

️✔️latest

️✔️3.10

️✔️3.9

️✔️sqlvm

️✔️latest

️✔️3.10

️✔️3.9

️✔️storage

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️synapse

️✔️latest

️✔️3.10

️✔️3.9

️✔️telemetry

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

️✔️util

️✔️latest

️✔️3.10

️✔️3.9

️✔️vm

️✔️2018-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2019-03-01-hybrid

️✔️3.10

️✔️3.9

️✔️2020-09-01-hybrid

️✔️3.10

️✔️3.9

️✔️latest

️✔️3.10

️✔️3.9

[zhoxing-ms]

@albertofori Could you please resolve these conflicts?

[albertofori]

@albertofori Could you please resolve these conflicts?

Hi @zhoxing-ms Please a change has been pushed to resolve the merge conflicts, thanks!

[zhoxing-ms]

@albertofori Thanks for the quick response, we will release this PR in the next breaking change release (on 05-23)

[zhoxing-ms]

@albertofori Albert Ofori FTE Could you please resolve these conflicts?

[albertofori]

@albertofori Albert Ofori FTE Could you please resolve these conflicts?

@zhoxing-ms Please the conflicts have been resolved. Thanks!