-
Notifications
You must be signed in to change notification settings - Fork 5.6k
[Synapse] Add Get Workspace, Read/List BigDataPools, SqlPools, IntegrationRuntimes API spec from the data-plane #10128
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
Conversation
[Staging] Swagger Validation Report
Only 10 items are listed, please refer to log for more details.
❌ |
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-js - Release
|
azure-sdk-for-net - Release
|
azure-sdk-for-go - Release
|
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
|
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-sdk-for-java - Release
|
|
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
|
|
Can one of the admins verify this patch? |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
specification/synapse/data-plane/Microsoft.Synapse/preview/2020-01-01-preview/bigDataPools.json
Outdated
Show resolved
Hide resolved
specification/synapse/data-plane/Microsoft.Synapse/preview/2020-01-01-preview/bigDataPools.json
Outdated
Show resolved
Hide resolved
|
Azure Pipelines successfully started running 1 pipeline(s). |
specification/synapse/data-plane/Microsoft.Synapse/preview/2020-01-01-preview/bigDataPools.json
Outdated
Show resolved
Hide resolved
...ion/synapse/data-plane/Microsoft.Synapse/preview/2020-01-01-preview/integrationRuntimes.json
Outdated
Show resolved
Hide resolved
specification/synapse/data-plane/Microsoft.Synapse/preview/2020-01-01-preview/sqlPools.json
Outdated
Show resolved
Hide resolved
specification/synapse/data-plane/Microsoft.Synapse/preview/2020-01-01-preview/workspace.json
Outdated
Show resolved
Hide resolved
|
|
|
Azure Pipelines successfully started running 1 pipeline(s). |
2 similar comments
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…nsSuffix parameter
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-resource-manager-schemas - Release
|
|
@cool-mist when I look at the LintDiff errors now, they seem legitimate: Otherwise I would reach out to @lmazuel. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@cool-mist please take a look at the BreakingChange failures. |
|
@tjprescott some of scheme definitions in artifacts.json are not used but they cause conflicts. So I removed them. |
|
@lmazuel will need to do the merge. I don't have the necessary permissions. |
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.