-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Added new DTC api version in V2022-05-01-preview #20395
Added new DTC api version in V2022-05-01-preview #20395
Conversation
Hi, @krivi37 Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected] |
Swagger Validation Report
|
compared swaggers (via Oad v0.9.7)] | new version | base version |
---|---|---|
ManagedInstanceDtcs.json | 2022-05-01-preview(07e4b7e) | 2022-02-01-preview(main) |
️⚠️
LintDiff: 0 Warnings warning [Detail]
compared tags (via openapi-validator v1.13.0) | new version | base version |
---|---|---|
package-preview-2022-05 | package-preview-2022-05(07e4b7e) | package-preview-2022-05(dev-sql-Microsoft.Sql-2022-05-01-preview) |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
The response of operation:'ManagedInstanceDtcs_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Sql/preview/2022-05-01-preview/ManagedInstanceDtcs.json#L62 |
|
The response of operation:'ManagedInstanceDtcs_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Sql/preview/2022-05-01-preview/ManagedInstanceDtcs.json#L113 |
️⚠️
Avocado: 1 Warnings warning [Detail]
Rule | Message |
---|---|
The default tag contains multiple API versions swaggers. readme: specification/sql/resource-manager/readme.md tag: specification/sql/resource-manager/readme.md#tag-package-composite-v5 |
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
SDK Track2 Validation succeeded [Detail]
- The following tags are being changed in this PR
- "https://github.com/Azure/azure-rest-api-specs/blob/07e4b7e5aa1543ee7b7a990dfa938f4ff346c114/specification/sql/resource-manager/readme.md#tag-package-preview-2022-05">sql/resource-manager/readme.md#package-preview-2022-05
Rule | Message |
---|---|
DuplicateOperation |
"readme":"sql/resource-manager/readme.md", "tag":"package-preview-2022-05", "details":"Duplicate Operation 'DatabaseSqlVulnerabilityAssessmentBaselines' > 'CreateOrUpdate' detected(This is most likely due to 2 operation using the same 'operationId' or 'tags'). Duplicates have those paths:\n - put /subscriptions/subscriptionId/resourceGroups/resourceGroupName/providers/Microsoft.Sql/servers/serverName/databases/databaseName/sqlVulnerabilityAssessments/vulnerabilityAssessmentName/baselines/baselineName\n - put /subscriptions/subscriptionId/resourceGroups/resourceGroupName/providers/Microsoft.Sql/servers/serverName/sqlVulnerabilityAssessments/vulnerabilityAssessmentName/baselines/baselineName" |
DuplicateOperation |
"readme":"sql/resource-manager/readme.md", "tag":"package-preview-2022-05", "details":"Duplicate Operation 'DatabaseSqlVulnerabilityAssessmentRuleBaselines' > 'Delete' detected(This is most likely due to 2 operation using the same 'operationId' or 'tags'). Duplicates have those paths:\n - delete /subscriptions/subscriptionId/resourceGroups/resourceGroupName/providers/Microsoft.Sql/servers/serverName/databases/databaseName/sqlVulnerabilityAssessments/vulnerabilityAssessmentName/baselines/baselineName/rules/ruleId\n - delete /subscriptions/subscriptionId/resourceGroups/resourceGroupName/providers/Microsoft.Sql/servers/serverName/sqlVulnerabilityAssessments/vulnerabilityAssessmentName/baselines/baselineName/rules/ruleId" |
|
"readme":"sql/resource-manager/readme.md", "tag":"package-preview-2022-05", "details":"Duplicate object schemas with 'SecurityAlertPolicyName' name detected." |
|
"readme":"sql/resource-manager/readme.md", "tag":"package-preview-2022-05", "details":"Error: 3 errors occured -- cannot continue." |
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
Swagger Generation Artifacts
|
Generated ApiView
|
Hi @krivi37, Your PR has some issues. Please fix the CI sequentially by following the order of
|
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
Hi, @krivi37 your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board([email protected]). |
...ation/sql/resource-manager/Microsoft.Sql/preview/2022-05-01-preview/ManagedInstanceDtcs.json
Show resolved
Hide resolved
Please ensure to respond feedbacks from the ARM API reviewer. When you are ready to continue the ARM API review, please remove |
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.
@xiaoxuqi-ms can you help to review and merge this PR? thanks~ |
[2022-05-01] Update parameter name of Database ARM API swagger changes for vbs enclaves (Azure#20606) * swagger changes for vbs enclaves * remove unreferenced json example * update name of parameter from enclaveType -> preferredEnclaveType * name change fix * fix json * added examples for update database with enclave type * add missing example file * fix spell check [2022-05-01] Database ARM API swagger changes for vbs enclaves (Azure#20413) * swagger changes for vbs enclaves * remove unreferenced json example Adding new Virtual Cluster APIs (Azure#20469) * adding new VC VNext APIs * fixing examples * fixing examples2 * doing this to kick of validation that's stuck * doing this to kick of validation that's stuck * removing not neede file Co-authored-by: Jovana Toroman <[email protected]> swagger and example files for new api GetSynapselinkWorkspaces (Azure#20377) * swagger and example files for new api * Update readme.md * Update custom-words.txt * Update GetSynapseLinkWorkspaces.json Fix databaseName spelling. * Update SynapseLinkWorkspaces.json regenerate swagger to fix spelling. * Update readme.md add to v5 package * update example file * Update GetSynapseLinkWorkspaces.json empty properties * Update SynapseLinkWorkspaces.json Use TrackedResource * Update SynapseLinkWorkspaces.json revert tracked resource * Update SynapseLinkWorkspaces.json * Update GetSynapseLinkWorkspaces.json only for testing. * Update GetSynapseLinkWorkspaces.json add properties back * Update GetSynapseLinkWorkspaces.json remove properties for testing only. * Update GetSynapseLinkWorkspaces.json add value to example file. * Update SynapseLinkWorkspaces.json add x-ms-identifier * Update GetSynapseLinkWorkspaces.json fix prettier text * remove get and use listbydatbases remove get and use listbydatbases * fix path of example file. fix path of example file. * Update SynapseLinkWorkspaces.json added new error codes. Added new DTC api version in V2022-05-01-preview (Azure#20395) * Added new examples and swagger for managed instance DTC * Fixed examples * Fixed examples typo, and added newer version to package composite v5 readme * Changed error messages and updated parameter descriptions Co-authored-by: Stefan Krivokapic <[email protected]> [SQL] 2022-05-01 DistributedAvailabilityGroups SetRole specs (Azure#20321) * Add DAG setRole swag docs * regenerate files * regenerate files * bump v5 tag * Update specification/sql/resource-manager/readme.md * Minor fix - update descriptions MI standby replica (Azure#20237) * Update InstanceFailoverGroups * Regenerate swagger Co-authored-by: Lazar Lazic <[email protected]> Managed Instance Long Term Retention Policy v20220501 (Azure#20099) * aupdate swagger files * fix validation break * fix validation error again * fix validation v3 ManagedDatabases 2022-05-01-preview update: ManagedDatabaseStatus (Azure#20114) * ManagedDatabases 2022-05-01-preview update: ManagedDatabaseStatus * Add Swaggers for API versions < 20220501 * Revert "Add Swaggers for API versions < 20220501" This reverts commit e3d4879. * Regenerate Swagger after the latest API changes * Regenerate Swagger after reverting the SwaggerEnum-name to "ManagedDatabaseStatus" Co-authored-by: Djordje Jeremic <[email protected]> ManagedDatabaseMoveOperations: Initial commit (Azure#20066) * ManagedDatabaseMoveOperations: Initial commit * fixup! ManagedDatabaseMoveOperations: Initial commit Co-authored-by: Djordje Jeremic <[email protected]> Added new managed database swagger and example (Azure#19954) Create dev branch dev-sql-Microsoft.Sql-2022-05-01-preview (Azure#19915) * Adds base for updating Microsoft.Sql from version preview/2022-02-01-preview to version 2022-05-01-preview * Updates readme * Updates API version in new specs and examples * revert the default tag
ARM API Information (Control Plane)
Changelog
Add a changelog entry for this PR by answering the following questions:
What's the purpose of the update?
This change, introduces 2 new properties in managed instance DTC security settings. Those 2 properties are optional integers - xaTransactionsDefaultTimeout and xaTransactionsMaximumTimeout. The version bump is not visible on this PR, since this is a dev branch in which all the controllers from the previous version are copied and have their API version bumped.
The newly generated clients will be able to set the mentioned properties when updating the managed instance DTC, and those 2 properties will be visible when fetching the managed instance's DTC. Since they are optional, they can be omitted in the request - the underlying resource won't change/replace them if they are missing.
When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month. - Next month
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month. -Next month
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.
Contribution checklist (MS Employees Only):
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.