Skip to content

Review request for Microsoft.DBforPostgreSQL to add version preview/2025-01-01-preview#33028

Merged
nasc17 merged 29 commits intoAzure:mainfrom
nasc17:nasc/postgresqlV20250101
Apr 30, 2025
Merged

Review request for Microsoft.DBforPostgreSQL to add version preview/2025-01-01-preview#33028
nasc17 merged 29 commits intoAzure:mainfrom
nasc17:nasc/postgresqlV20250101

Conversation

@nasc17
Copy link
Member

@nasc17 nasc17 commented Mar 5, 2025

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!

  • [ X] 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).

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:

  • [X ] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
  • [C ] 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.

Additional information

Viewing API changes
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.

@nasc17 nasc17 added the PublishToCustomers Acknowledgement the changes will be published to Azure customers. label Mar 5, 2025
@nasc17 nasc17 requested review from a team, msyyc, qiaozha and tadelesh as code owners March 5, 2025 21:47
@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Mar 5, 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 Mar 5, 2025

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

@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 Mar 5, 2025
@azure-sdk
Copy link
Collaborator

azure-sdk commented Mar 5, 2025

API Change Check

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

Language API Review for Package
Swagger Microsoft.DBforPostgreSQL

@AzureRestAPISpecReview AzureRestAPISpecReview added BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required NotReadyForARMReview and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Mar 6, 2025
@JiaqiZhang-Dev
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.

@nasc17
Copy link
Member Author

nasc17 commented Mar 20, 2025

Removed BreakingChange-Go-Sdk, passing in checks

@microsoft-github-policy-service microsoft-github-policy-service bot added the no-recent-activity There has been no recent activity on this issue. label Apr 7, 2025
@openapi-pipeline-app
Copy link

PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts.

@microsoft-github-policy-service microsoft-github-policy-service bot removed the no-recent-activity There has been no recent activity on this issue. label Apr 15, 2025
…quent characters in a name can be letters, digits (0-9), or underscores. Database name length must be less than 32 characters
@openapi-pipeline-app
Copy link

PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts.

@nasc17
Copy link
Member Author

nasc17 commented Apr 29, 2025

@msyyc could you please review?

Copy link
Member

@msyyc msyyc left a comment

Choose a reason for hiding this comment

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

I am Python SDK owner. Approved for python.

@nasc17 nasc17 merged commit b7df812 into Azure:main Apr 30, 2025
45 of 49 checks passed
koen-mertens pushed a commit to koen-mertens/azure-rest-api-specs that referenced this pull request May 7, 2025
…025-01-01-preview (Azure#33028)

* Copy over previous preview api

* Update versions

* Updae readmes

* Update title name

* Update examples

* Update descriptions

* Update Tuning Options

* DbTuning Init

* fix semantic error

* Lint Diff Fixes

* Lint Diff Warnings

* Update tuning params and examples

* tuning configuration and index fixes

* lint fixes

* lint fixes

* remove "x-ms-client-flatten": true,

* lint fixes

* Lint fixes

* revert lint warning change

* Add suppresion for tuning options api

* update readme

* Remove multi default api

* Fix suppresion paths, cleanup readme

* Revert "Fix suppresion paths, cleanup readme"

This reverts commit 4c79ff5.

* Put back single sever

* Add missing server states

* Database name must begin with a letter (a-z) or underscore (_). Subsequent characters in a name can be letters, digits (0-9), or underscores. Database name length must be less than 32 characters

* revert change, not preview in TS.
@TimLovellSmith
Copy link
Member

@gary-x-li @mikeharder is there some known issue with Avocado here for which avocado was suppressed?

@mikeharder
Copy link
Member

@gary-x-li @mikeharder is there some known issue with Avocado here for which avocado was suppressed?

Azure/avocado#152

@kazrael2119
Copy link
Member

@nasc17 I noticed that your readme tag is incorrect and missing typescript configs for this version
I create a PR #34762 to fix it, could you help review?

BTW, please always remember to add the new flexible config in readme.typescript.md if you add a new flexible tag so that we can review if the new version has breaking changes

thanks

nwnt pushed a commit to nwnt/azure-rest-api-specs that referenced this pull request Jun 10, 2025
…025-01-01-preview (Azure#33028)

* Copy over previous preview api

* Update versions

* Updae readmes

* Update title name

* Update examples

* Update descriptions

* Update Tuning Options

* DbTuning Init

* fix semantic error

* Lint Diff Fixes

* Lint Diff Warnings

* Update tuning params and examples

* tuning configuration and index fixes

* lint fixes

* lint fixes

* remove "x-ms-client-flatten": true,

* lint fixes

* Lint fixes

* revert lint warning change

* Add suppresion for tuning options api

* update readme

* Remove multi default api

* Fix suppresion paths, cleanup readme

* Revert "Fix suppresion paths, cleanup readme"

This reverts commit 4c79ff5.

* Put back single sever

* Add missing server states

* Database name must begin with a letter (a-z) or underscore (_). Subsequent characters in a name can be letters, digits (0-9), or underscores. Database name length must be less than 32 characters

* revert change, not preview in TS.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved-Avocado Approved-Suppression 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 SuppressionReviewRequired

Projects

None yet

Development

Successfully merging this pull request may close these issues.