-
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
Adding PowerPlatform swagger. #10651
Conversation
[Staging] Swagger Validation Report
️✔️ |
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-python - Release
|
Azure CLI Extension Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-resource-manager-schemas - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-go - Release
|
azure-sdk-for-net - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Trenton Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-python-track2 - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
@rapatank, please fix the CI check failures. |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
@rapatank , could you reply chiragg4u if you complete above ask to start ARM review? |
...orm/resource-manager/Microsoft.PowerPlatform/preview/2020-10-30-preview/subnetResources.json
Outdated
Show resolved
Hide resolved
...orm/resource-manager/Microsoft.PowerPlatform/preview/2020-10-30-preview/subnetResources.json
Show resolved
Hide resolved
Azure Pipelines successfully started running 1 pipeline(s). |
} | ||
} | ||
}, | ||
"Subnet": { |
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.
Subnet [](start = 5, length = 6)
I assume you are modeling it as a network subnet resource have you reviewed the network swagger definitions
specification\network\resource-manager\Microsoft.Network\stable\2018-11-01\virtualNetwork.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.
yes
...ce-manager/Microsoft.PowerPlatform/preview/2020-10-30-preview/privateEndpointConnection.json
Outdated
Show resolved
Hide resolved
Please resolve the model validation failures |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
"$ref": "../../common/v1/definitions.json#/parameters/ResourceGroupNameParameter" | ||
}, | ||
{ | ||
"$ref": "../../common/v1/definitions.json#/parameters/ApiVersionParameter" |
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.
This reference doesn't exist now and also needs to be updated.
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.
thanks! done
"$ref": "../../../../../common-types/resource-management/v1/types.json#/parameters/SubscriptionIdParameter" | ||
}, | ||
{ | ||
"$ref": "../../common/v1/definitions.json#/parameters/ApiVersionParameter" |
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.
Same here.
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.
done
"operationId": "Operations_List", | ||
"parameters": [ | ||
{ | ||
"$ref": "../../common/v1/definitions.json#/parameters/ApiVersionParameter" |
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.
Same here.
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.
done, thanks!
Azure Pipelines successfully started running 1 pipeline(s). |
}, | ||
"description": "An error response from the PowerPlatform service." | ||
}, | ||
"Resource": { |
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.
As commented in different file; these should refer to global common definitions rather than copying locally.
] | ||
} | ||
}, | ||
"/providers/Microsoft.PowerPlatform/operations": { |
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.
"/providers/Microsoft.PowerPlatform/operations" [](start = 0, length = 51)
Nit: Normally operations API's are kept in the main swagger file.
Looked at the changes, API's seems to be OK and has been reviewed by the team internally. Marking ARMSignOff based on the discussion. |
* PowerPlatform RP specifications * PowerPlatform changes * Updating powerplatform json * Update definitions.json * Updating the schema * Updated the schema. * Updates to schema * Schema update * Schema update * Example update * Update description * Updating the swagger * Updating the swagger definition * Swagger update. * Swagger updates * Adding private link changes. * Updates to readme.md * Private link updates * Schema update * private link update * response update * Added systemData * Updated description. * Adding subnet configuration * readme update. * Adding systemData. * Updated example * Update * Update to systemData * Updates * Updates * Updated the version of common types * readme.go update * Update * Updated version * version update * update * update * Updated "enterprisePromise" to "enterprisePolicy". * Updates * Updates * Updating to use common type * updates
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
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 there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.