-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Calec/new api version #24542
Calec/new api version #24542
Conversation
…into calec/new-api-version
Hi, @calecarter 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. vscswagger@microsoft.com |
Swagger Generation Artifacts
|
Generated ApiView
|
Hi @calecarter! For review efficiency consideration, when creating a new API version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version. |
Hi @calecarter! Your PR has some issues. Please fix the CI issues, if present, in following order:
If you need further help, please reach out on the Teams channel aka.ms/azsdk/support/specreview-channel. #Resolved |
js sdk generation failure is a known issue |
Swagger pipeline restarted successfully, please wait for status update in this comment. |
* Baseline current api version * Add new version properties/apis * Add new list apis * Sync with main * Update readme files * Updated python readme * reverting to sync with main * updating python and main readme * Fixing some automation failures * add examples for all policyDefinitionVersion apis * Add examples for policy set versions * Updated readme to remove tangling tag * Fix linter issues and and suppression where applicable * Fix linter errors for assignmenets swagger * Fix more linter errors * fix more linter errors * Add schema property to definition parameters to reflect reality * Fix prettier check issues * Updated based on feedback * Fixing linter errors * Fixed more linter errors * Fix JSON syntax error * updated based on feedback to remove RepeatedPathInfo subpression for new apis * Updated subid and api version to use common types
input-file: | ||
- Microsoft.Authorization/stable/2020-09-01/dataPolicyManifests.json | ||
- Microsoft.Authorization/stable/2023-04-01/policyDefinitions.json | ||
- Microsoft.Authorization/stable/2023-04-01/policyDefinitionVersions.json | ||
- Microsoft.Authorization/stable/2023-04-01/policySetDefinitions.json | ||
- Microsoft.Authorization/stable/2023-04-01/policySetDefinitionVersions.json | ||
- Microsoft.Authorization/stable/2023-04-01/policyAssignments.json | ||
- Microsoft.Authorization/preview/2022-07-01-preview/policyExemptions.json | ||
- Microsoft.Authorization/preview/2022-08-01-preview/policyVariables.json | ||
- Microsoft.Authorization/preview/2022-08-01-preview/policyVariableValues.json |
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.
One tag shall only contain one api-version, otherwise it will cause Python SDK generation failure.
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.
Can you elaborate? This tag has a single api-version for each type.
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.
ARM (Control Plane) API Specification Update Pull Request
Purpose of this PR
What's the purpose of this PR? Check all that apply. 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 request review from an ARM API Review board.
ARM API changes review
ARMReview
label.ARMReview
label, if appropriate.If this happens, proceed according to guidance given in GitHub comments also added by the automation.
Breaking change review
If you have any breaking changes as defined in the Breaking Change Policy,
follow the process outlined in the High-level Breaking Change Process doc.
Getting help
and https://aka.ms/ci-fix.