Review request for Microsoft.DBforPostgreSQL to add version preview/2025-01-01-preview#33028
Review request for Microsoft.DBforPostgreSQL to add version preview/2025-01-01-preview#33028nasc17 merged 29 commits intoAzure:mainfrom
Conversation
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
|
PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
|
/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. |
|
Removed BreakingChange-Go-Sdk, passing in checks |
|
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
…quent characters in a name can be letters, digits (0-9), or underscores. Database name length must be less than 32 characters
|
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
|
@msyyc could you please review? |
msyyc
left a comment
There was a problem hiding this comment.
I am Python SDK owner. Approved for python.
…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.
|
@gary-x-li @mikeharder is there some known issue with Avocado here for which avocado was suppressed? |
|
|
@nasc17 I noticed that your readme tag is incorrect and missing typescript configs for this version 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 |
…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.
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
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.