-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Added new API version 2026-01-01-preview to Microsoft.DBforPostgreSQL #38674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
jperovic
merged 5 commits into
Azure:main
from
jperovic:dev/jovanperovic/migrate-network-mode-spec
Nov 28, 2025
Merged
Added new API version 2026-01-01-preview to Microsoft.DBforPostgreSQL #38674
jperovic
merged 5 commits into
Azure:main
from
jperovic:dev/jovanperovic/migrate-network-mode-spec
Nov 28, 2025
Conversation
This file contains hidden or 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
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.Comment generated by summarize-checks workflow run. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
Member
Author
|
/azp run |
|
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. |
Member
Author
|
/azp run SDK Validation - Go, SDK Validation - Python, SDK Validation - .NET, SDK Validation - Java, SDK Validation - JS |
|
Azure Pipelines successfully started running 5 pipeline(s). |
Member
Author
|
/azp run SDK Validation Status |
|
No pipelines are associated with this pull request. |
e340979 to
8b17aa2
Compare
d50d58a to
cd6320b
Compare
cd6320b to
718265b
Compare
ravimeda
approved these changes
Nov 20, 2025
b52074d to
da79f2f
Compare
Updated operationId and tags Modified API response Added API example Some tweaks to API Added example for HTTP 200 Updated bad operationId in AdvancedThreatProtectionSettings Moving MigrateNetwork to Servers operations Changed operation description, removed MigrateNetwork.json from input Fixed bad filename Reverting changes to AdvancedThreatProtectionSettings.json Reapply "Reverting changes to AdvancedThreatProtectionSettings.json" This reverts commit fa18e53. Added state to MigrateNetworkStatus response Revert "Reverting changes to AdvancedThreatProtectionSettings.json" This reverts commit ed28203. Adding supression for BC-break ModifiedOperationId from Servers.json Revert "Adding supression for BC-break ModifiedOperationId from Servers.json" This reverts commit d5d07c1. Upgraded the default tag
da79f2f to
4dc47a5
Compare
nachoalonsoportillo
approved these changes
Nov 28, 2025
Member
nachoalonsoportillo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
lmazuel
pushed a commit
that referenced
this pull request
Dec 2, 2025
…#38674) * Base files for 2026-01-01-preview API version * Replacing occurrence of 2025-08-01 with 2026-01-01-preview * Adding a new API spec file Updated operationId and tags Modified API response Added API example Some tweaks to API Added example for HTTP 200 Updated bad operationId in AdvancedThreatProtectionSettings Moving MigrateNetwork to Servers operations Changed operation description, removed MigrateNetwork.json from input Fixed bad filename Reverting changes to AdvancedThreatProtectionSettings.json Reapply "Reverting changes to AdvancedThreatProtectionSettings.json" This reverts commit fa18e53. Added state to MigrateNetworkStatus response Revert "Reverting changes to AdvancedThreatProtectionSettings.json" This reverts commit ed28203. Adding supression for BC-break ModifiedOperationId from Servers.json Revert "Adding supression for BC-break ModifiedOperationId from Servers.json" This reverts commit d5d07c1. Upgraded the default tag * Updated API description * Modifed 202 description. Sorted enum item in RecommendationType --------- Co-authored-by: Jovan Perovic <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Approved-Avocado
ARMReview
ARMSignedOff
<valid label in PR review process>add this label when ARM approve updates after review
BreakingChange-Approved-Benign
Changes are not breaking at the REST API level and have at most minor impact to generated SDKs.
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
PostgreSQL
PublishToCustomers
Acknowledgement the changes will be published to Azure customers.
resource-manager
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
Tip
Overwhelmed by all this guidance? See the
Getting helpsection 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.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. 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 proceed to the diagram Step 2, "ARM API changes review", for this PR.
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 ApiViewcomment 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
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.