replacing modified swagger files in V20230201 after adding new controllers for Sql Data Classification APIs #24742
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, @pmahanandire! Thank you for your pull request. To help get your PR merged: Generated ApiView comment added to this PR. You can use ApiView to show API versions diff. |
Swagger Generation Artifacts
|
Generated ApiView
|
ghost
added
the
pmahanandire
changed the base branch from
main
to
release-sql-Microsoft.Sql-2023-02-01-preview
This was referenced Jul 10, 2023
AzureRestAPISpecReview
added
BreakingChangeReviewRequired
|
Hi @pmahanandire! The automation detected breaking changes in this pull request. As a result, it added the |
pmahanandire
requested review from
jamestao,
ericshape and
jeremyfrosti
as code owners
|
Hi, @pmahanandire. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
microsoft-github-policy-service
bot
added
no-recent-activity
and removed
no-recent-activity
labels
|
Hi, @pmahanandire. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
JeffreyRichter
added
the
Approved-BreakingChange
jeremyfrosti
added
WaitForARMFeedback
ms-zhenhua
added
ARMSignedOff
|
this js sdk breaking is not caused by this pr |
tadelesh
added
the
Approved-SdkBreakingChange-Go
|
/pr RequestMerge |
|
@pmahanandire thanks for this PR - I've taken a look into importing this one and it appears there's still a couple of references to the older constant name which are causing us issues:
In addition it appears there's an issue with the new On a related note, we're noticing the same issues with these particular constants also exist for the Synapse service too, I understand that's a separate Resource Provider, but I'm unclear if SQL and Synapse are maintained by different teams / who we'd need to reach out to in order to get that one fixed, does the SQL Team own that Resource Provider too? Tagging a couple of upstream issues on our side, so we can cross-reference this:
cc @WodansSon for info |
This was referenced Aug 9, 2023
rkmanda
merged commit 84dfcd3
into
Azure:release-sql-Microsoft.Sql-2023-02-01-preview
26 of 34 checks passed
ms-henglu
pushed a commit
that referenced
this pull request
Aug 23, 2023
* Adds base for updating Microsoft.Sql from version preview/2022-11-01-preview to version 2023-02-01-preview * Updates readme * Updates API version in new specs and examples * add mi refresh API (#24093) * add mi refresh API * remove stray character * add examples * fix lro error * fix lro error only in example * fixing prettier issue * Test commit - adding error schema * Test2 * Test - changing error type * Revert "Test - changing error type" This reverts commit 84fff94. * Reverting 3 test commits * Test - adding commong error type reference * fix type format errors --------- Co-authored-by: Stefan Krivokapic <skrivokapic@microsoft.com> * Adding changes from main to release branch. PRs 24175 and 24185 (#24221) * Enable multiple partner servers and failover of read-only endpoint for SQL DB Failover Group in version 2023-02-01-preview. (#24132) * Added the swagger spec and example json files for failvoer group API update in V2023-020-1 * Corrected the FailoverGroupGet.json example * Updated the auto-generated FailoverGroups.json Fixed FailoverGroups.json swagger arm-id attribute for databases field * Added the missing headers field manually * Fix FailoverGroups.json --------- Co-authored-by: Sharan Singh <sharanlobana@gmail.com> * Changes to Location Capabilities (#24209) * Loc cap changes * removing changes not related to my changes in dsmain * DAG API 2023-02-01 (#24108) * add new dag api version * Update swagger * Update swagger * patch resource * make replicationMode writable * Add FreeLimitExhaustion Capability in 2023-02-01-preview API (#24224) * Add FreeLimitExhaustion Capability in 2023-02-01-preview API * Change property from name to exhaustionBehaviorType * generate swagger for LocationCapabilites (#24290) * inital commit for LTR Policy Immutability (#24347) * inital commit for immutable ltr backups (#24349) * Update Servers swagger files with adding property "IsIPv6Enabled" (#24305) * Update swagger files for Server API * Add v5 tag for Servers * Restore none for minimal TLS version * Add auto rotation param to databases api (#24339) * Add auto rotation param to databases api * add armid * Adding IsFreemium and CreateTime to Get MI API (#24239) * Updated the examples for LTR Policies and LTR Backups (#24821) * Updated the examples for LTR Policies and LTR Backups * Not sure why makeBackupsImmutable got deleted * updating swagger files for enum name changes (#24742) * Carrying over minor changes for the 2023-02-01-preview release (#25177) * Carrying over minor changes for the 2023-02-01-preview release * Reverting example files that didn't have DsMainDev side changes, and fixing prettier check * Fixes for LTR examples with model validation and prettier check for ServerDelete * Reverting LTR changes * Adding arm-id to serversjson * swagger changes for adding new parameter in dc telemetry (#24834) * testing push * reverting push * swagger files for DC add parameter change * delete added file * modified swagger files without Venkat's change * modified swagger files * changed modelAsString to true * add example files * add example files * fix mismatch * Removing Pattern from ManagedInstance to avoid incident (#25295) * Carrying over minor changes for the 2023-02-01-preview release * Reverting example files that didn't have DsMainDev side changes, and fixing prettier check * Fixes for LTR examples with model validation and prettier check for ServerDelete * Reverting LTR changes * Adding arm-id to serversjson * Removing the Pattern property from ManagedInstances.json as it should not be present and will cause issues in downstream client generation --------- Co-authored-by: guptanitish-ms <68623376+guptanitish-ms@users.noreply.github.com> Co-authored-by: Stefan Krivokapic <skrivokapic@microsoft.com> Co-authored-by: lobashh <56324552+lobashh@users.noreply.github.com> Co-authored-by: Sharan Singh <sharanlobana@gmail.com> Co-authored-by: Aleksand4rZivanovic <60347245+Aleksand4rZivanovic@users.noreply.github.com> Co-authored-by: a-lazarlazic <106240189+a-lazarlazic@users.noreply.github.com> Co-authored-by: mykolian <34487118+mykolian@users.noreply.github.com> Co-authored-by: Srna Nikolic <133877309+srnanikolicmdcs@users.noreply.github.com> Co-authored-by: rebeccaxu-ms <104461363+rebeccaxu-ms@users.noreply.github.com> Co-authored-by: LeiWang3 <84884417+LeiWang3@users.noreply.github.com> Co-authored-by: viparek <78561564+viparek@users.noreply.github.com> Co-authored-by: Nikola Mirkovic <135128634+nmirkovic-microsoft@users.noreply.github.com> Co-authored-by: pmahanandire <104351468+pmahanandire@users.noreply.github.com> Co-authored-by: nidhigupta <139312437+Nidhi-Gupta6198@users.noreply.github.com>
|
@tombuildsstuff, could you please elaborate on the issues caused by the older constant name, because after this change, the enum names and the values they take are consistent. |
6 tasks
|
@pmahanandire, I have linked @tombuildsstuff PR(#26303) to fix the remaining issue for Pandora SDK import. |
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ARM (Control Plane) API Specification Update Pull Request
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can request review from an ARM API Review board.
ARM API changes review
ARMReviewlabel.ARMReviewlabel, if appropriate.If this happens, proceed according to guidance given in GitHub comments also added by the automation.
Breaking change review
If you have any breaking changes as defined in the Breaking Change Policy,
follow the process outlined in the High-level Breaking Change Process doc.
Getting help
and https://aka.ms/ci-fix.