When moving to a new major version, preserve all default API versions of the previous one #3424
Labels
3.0
impact/usability
Something that impacts users' ability to use the product easily and intuitively
kind/enhancement
Improvements or new features
resolution/fixed
This issue was fixed
Milestone
When Azure API version 2022-01-01 is the default for a resource in v2, and in v3 the new default is 2024-01-01, then the previous default 2022-01-01 should still be available in v3 as an explicit import. That enables to upgrade without changes, other than import paths.
We had already planned that for v2 but missed.
The text was updated successfully, but these errors were encountered: