-
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
Fix S360 items for FSPG swagger #16727
Conversation
…I 2021-06-01, 2021-06-01-preview, and 2021-06-15-privatepreview
… and 2021-06-01 APIs
Hi, @xunsun-commits 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] |
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Swagger Validation Report
|
Swagger Generation Artifacts
|
Hi @xunsun-commits, Your PR has some issues. Please fix the CI sequentially by following the order of
|
...gresql/resource-manager/Microsoft.DBforPostgreSQL/preview/2021-06-01-preview/postgresql.json
Outdated
Show resolved
Hide resolved
Hi @xunsun-commits, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
NewApiVersionRequired reason: |
/azp run |
* Changed FSPG RestartParameter.failoverMode from string to enum for API 2021-06-01, 2021-06-01-preview, and 2021-06-15-privatepreview * Change enum first letter to lower case * Change to upper case * Fix S360 bugs for swagger FSPG 2020-02-14-preview, 2021-06-01-preview and 2021-06-01 APIs * Fix S360 item by adding default value to backupRetentionDays and maintenanceWindow * Fix s360 bugs * Undo supportedIops change, will change in RP side * Fix NameAvailability and ConfigurationProperties s360 bugs * Fix s360 bug for CloudError * Undo CloudError fix * Fix string default value * Remove server.tags because TrackedResource already has tags
S360 items:
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=0219BFDB-C067-47C6-820C-1CA1EEBA406E
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=B9AD5DBC-61EA-4026-9F4A-71E5E8599121
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=1D576149-7BA8-4FC1-B9FD-3EFADF8D02F3
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=C39B35F6-8502-43A1-AA1B-600020A90B3D
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=1DFDD69E-13BB-4F3E-93E1-7F61DD2F1784
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=0A625C05-2A91-4205-BF8E-7FA90F63144A
https://portal.azure-devex-tools.com/amekpis/correctness/detail?errorId=61BAF9D5-A927-4DD2-A2DE-A25A1D94DEF9
Breaking change intake:
https://msazure.visualstudio.com/One/_workitems/edit/12564731
The fix are:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
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 label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[ ] 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.
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 any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.