Skip to content

Release sql microsoft.sql 2024 11 01 preview version#35794

Merged
lirenhe merged 11 commits intomainfrom
publish-sql-Microsoft.Sql-2024-11-01-preview
Jul 17, 2025
Merged

Release sql microsoft.sql 2024 11 01 preview version#35794
lirenhe merged 11 commits intomainfrom
publish-sql-Microsoft.Sql-2024-11-01-preview

Conversation

@achyuth-ms
Copy link
Member

@achyuth-ms achyuth-ms commented Jul 9, 2025

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

spec_pr_review_workflow_diagram

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

  • New resource provider.
  • New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
  • Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
  • Update existing version to fix OpenAPI spec quality issues in S360.
  • Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
  • Other, please clarify:
    • edit this with your clarification

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:

  • I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
  • I have reviewed following Resource Provider guidelines, including
    ARM resource provider contract and
    REST guidelines (estimated time: 4 hours).
    I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
  • A release plan has been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

  • First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
  • If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
  • To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
  • For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
    and https://aka.ms/ci-fix.
  • For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
  • If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
    This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
  • If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.
  • For guidance on SDK breaking change review, refer to https://aka.ms/ci-fix.

achyuth-ms and others added 7 commits May 13, 2025 17:07
…rsion.ps1 (#34664)

* Copy files from preview/2024-05-01-preview

Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.

* Update version to preview/2024-11-01-preview

Updated the API version from preview/2024-05-01-preview to preview/2024-11-01-preview.

* Added tag for 2024-11-01-preview in readme file

* Update readme.md

revert default tag
…Protector (#34785)

* database, serverKey, EncryptionProtector

* prettier fix

* fix un-referenced JSON file
* swagger 2024 11 01 ltr immutability

* Fix prettier

* Fix spelling

* add missing files and update examples by truncating miliseconds and add extra white line in the end for prettier check

* Fix prettier

* change archive to Hot

* Remove dupe backup

* Add Hot to backup names and changed 8 POST requests example responses

* Fix prettier

* Fix duplicate operation ID
* Swagger changes related to Suspend/Resume effort in SQL MI

* Altered Inaccessible Uri to inaccessible Uri field + changed int to string in example

---------

Co-authored-by: Andrija Veljkovic <aveljkovic@microsoft.com>
* Add Swagger API to support TDE Suspend Resume feature

* Fix transparent data encryptions json to not include Created

* Remove 201 response from example files as its not required.

* Remove suspend resume json from core folder and add it to examples folder

---------

Co-authored-by: Mayank Gupta <mayangupta@microsoft.com>
* swagger update 2024-11-01

* small invalid type fix
@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Jul 9, 2025

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Jul 9, 2025

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

@achyuth-ms achyuth-ms changed the title Publish sql microsoft.sql 2024 11 01 preview Release sql microsoft.sql 2024 11 01 preview version Jul 9, 2025
@github-actions github-actions bot added the brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. label Jul 9, 2025
@github-actions
Copy link

github-actions bot commented Jul 9, 2025

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
Swagger common
Go sdk/resourcemanager/sql/armsql
Python azure-mgmt-sql
Java com.azure.resourcemanager:azure-resourcemanager-sql-generated

@AzureRestAPISpecReview AzureRestAPISpecReview added ARMReview BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required new-api-version NotReadyForARMReview resource-manager labels Jul 9, 2025
@mikekistler mikekistler added the BreakingChange-Approved-Previously Changes were reviewed and approved in a previous PR label Jul 11, 2025
@razvanbadea-msft
Copy link
Member

/azp run

@azure-pipelines
Copy link

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

@AzureRestAPISpecReview AzureRestAPISpecReview added WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required and removed NotReadyForARMReview labels Jul 11, 2025
Copy link
Member

@ericshape ericshape left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
and approved from SQL RP

@psah434
Copy link
Member

psah434 commented Jul 15, 2025

Please fix all swagger avocado and lintdiff errors.

@ericshape ericshape enabled auto-merge (squash) July 17, 2025 00:38
@AzureRestAPISpecReview AzureRestAPISpecReview removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jul 17, 2025
@ericshape ericshape removed the BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required label Jul 17, 2025
@ericshape
Copy link
Member

remove breaking change review label 'cause we have got the breaking change reviewer's approval tag.

@ericshape ericshape added PublishToCustomers Acknowledgement the changes will be published to Azure customers. Approved-ModelValidation labels Jul 17, 2025
@ericshape
Copy link
Member

we have got ARM reviewer sign off

@ericshape ericshape disabled auto-merge July 17, 2025 03:50
@ericshape ericshape enabled auto-merge (squash) July 17, 2025 03:50
@ericshape ericshape disabled auto-merge July 17, 2025 03:51
@ericshape ericshape enabled auto-merge (rebase) July 17, 2025 03:51
@ericshape ericshape disabled auto-merge July 17, 2025 04:04
@ericshape ericshape enabled auto-merge (squash) July 17, 2025 04:04
@ericshape ericshape self-assigned this Jul 17, 2025
@ericshape ericshape disabled auto-merge July 17, 2025 04:27
@ericshape ericshape enabled auto-merge (squash) July 17, 2025 04:27
@ericshape ericshape self-requested a review July 17, 2025 07:04
@AzureRestAPISpecReview AzureRestAPISpecReview added the BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required label Jul 17, 2025
@lirenhe
Copy link
Member

lirenhe commented Jul 17, 2025

Force merge this PR as the JS failure is an internal issue and not related to this change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved-Avocado Approved-LintDiff Approved-ModelValidation ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review BreakingChange-Approved-Previously Changes were reviewed and approved in a previous PR BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. new-api-version PipelineBotTrigger PublishToCustomers Acknowledgement the changes will be published to Azure customers. resource-manager SQL

Projects

None yet

Development

Successfully merging this pull request may close these issues.