API / schema versioning strategy for Microsoft.Sql resource provider #1486
Comments
ghost
added
the
|
Hello @azureSQLGitHub! It looks like there is a schemas issue that needs your attention. Please investigate and confirm it is on your end. Thanks 😄 Issue DetailsThe Azure REST API Guidelines describe the use of preview APIs and states preview APIs are not subject to the same stability or lifecycle guarantees as generally available APIs. Additionally the guidelines state preview APIs should be retired within 12 months. When deploying SQL resources via ARM tempalte from the Microsoft.Sql resource provider, the most recent stable API version is What strategy is the Microsoft.Sql resource provider team taking when versioning their API / schema?
|
|
Hi @MWL88 this is an RP specific issue relating to their process of releasing preview api versions. We will discuss internally with the SQL team to see what can be done here. |
|
Hi @apclouds - is there anything you can share about the outcome of those discussions? Alternatively, should we be raising an issue elsewhere in order to get this resolved? Thanks! |
|
Looks like there's at least two other RPs in a similar situation: |
The Azure REST API Guidelines describe the use of preview APIs and states preview APIs are not subject to the same stability or lifecycle guarantees as generally available APIs. Additionally the guidelines state preview APIs should be retired within 12 months.
When deploying SQL resources via ARM tempalte from the Microsoft.Sql resource provider, the most recent stable API version is
2015-05-01(almost 6 years ago) and all subsequent API versions have been marked as preview.What strategy is the Microsoft.Sql resource provider team taking when versioning their API / schema?
Is there any documentation describing how customers should interpret the Microsoft.Sql API versions to identify stable and preview APIs?
The text was updated successfully, but these errors were encountered: