Need a central place to record the Azure cli api-version change #16094
Description
Is your feature request related to a problem? Please describe.
My problem is very similar to: #9834, #12881, #12895, #13047
The azure cli complains that:
cli.azure.cli.core.util : NoRegisteredProviderFound - No registered resource provider found for location 'chinanorth' and API version '2019-06-15-preview' for type 'profiles/endpoints'. The supported api-versions are '2015-06-01, 2016-04-02, 2016-10-02, 2017-04-02, 2017-10-12, 2018-04-02, 2019-04-15'. The supported locations are 'chinanorth, chinanorth2, chinaeast, chinaeast2'.
NoRegisteredProviderFound - No registered resource provider found for location 'chinanorth' and API version '2019-06-15-preview' for type 'profiles/endpoints'. The supported api-versions are '2015-06-01, 2016-04-02, 2016-10-02, 2017-04-02, 2017-10-12, 2018-04-02, 2019-04-15'. The supported locations are 'chinanorth, chinanorth2, chinaeast, chinaeast2'.
It looks like Azure Cli use an api-version which is not supported by the backend resource provider. And the mitigation is often to downgrade the azure cli version. But we do not have a central place to record the api-version change and it is not easy to know which cli version should we use.
Describe the solution you'd like
The ideal solution is that we could specify the api-version in the command.
Describe alternatives you've considered
If the above solution is not acceptable, it would be great if we could have a central place to keep the api-version change history to help customer to choose the correct version to use.
Additional context