[Synapse Management] Update sqlPool.json and add integrationRuntime.json #8628
Conversation
|
Azure Pipelines successfully started running 1 pipeline(s). |
6 similar comments
|
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). |
|
Can one of the admins verify this patch? |
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-go - Release
|
azure-sdk-for-java - Release
|
azure-sdk-for-net - Release
|
azure-sdk-for-js - Release
|
azure-sdk-for-python - Release
|
07b2091 to
7bd348f
Compare
|
Azure Pipelines successfully started running 1 pipeline(s). |
7bd348f to
0dd8662
Compare
|
Azure Pipelines successfully started running 1 pipeline(s). |
0dd8662 to
afd6796
Compare
|
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
just curious, why use post get here? #Resolved
There was a problem hiding this comment.
If that is the case, then why are the body parameters not modeled in this swagger file?
Hi @anthony-c-martin , I am sorry for giving a wrong reason for why it it post.
I checked with backend team, they said it is a action instead of simply get resource, the action need to be audited and loged. So it is Post instead of Get. Thanks
There was a problem hiding this comment.
same as above
Checked with backend, this api requires parameters to be passed in the body.
There was a problem hiding this comment.
Do you have a default value for ttl?
There was a problem hiding this comment.
Do you have a default value for ttl?
No
2. add integrationRuntime.json and related example
afd6796 to
45d940b
Compare
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@yungezz , Can we remove WaitForARMFeedback label? ARM team has reviewed integrationRuntime.json and related example in Azure/azure-rest-api-specs-pr#1024 |
hi @arm-for-better, I compared integrationRuntime.json in this PR with the one in https://github.com/Azure/azure-rest-api-specs-pr/pull/1024/, there're lots of diffs including new operations like "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Synapse/workspaces/{workspaceName}/integrationRuntimes/{integrationRuntimeName}/disableInteractiveQuery", "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Synapse/workspaces/{workspaceName}/integrationRuntimes/{integrationRuntimeName}/removeNode": { |
Ok, It makes sense to me. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-cli-extensions - 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
|
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
@anthony-c-martin could you please help do the ARM review? we are blocked on ARM review for a long time. Thanks in advance. |
| exportdevices | ||
| exporterrors | ||
| exportstatus | ||
| Exprired |
There was a problem hiding this comment.
?
there is a property named "isIdentityCertExprired"
backend team said it's typo but they can't change it because it will cause breaking change. So in order to pass validation i have to add this as custom word
There was a problem hiding this comment.
This review hasn't been signed off on yet, so I don't see how it's possible to have a breaking change. Please ask the backend team to fix this.
There was a problem hiding this comment.
@fengzhou-msft, @yungezz is there any way to merge this PR in without adding Exprired to the custom-words list?
There was a problem hiding this comment.
@fengzhou-msft, @yungezz is there any way to merge this PR in without adding
Expriredto the custom-words list?
Hi @anthony-c-martin I have removed Exprired from the custom-words list and added it to cSpell.json to suppress spell check
| "type": "string" | ||
| } | ||
| }, | ||
| "additionalProperties": { |
There was a problem hiding this comment.
What additional properties are allowed here? Can they be modeled in swagger?
There was a problem hiding this comment.
What additional properties are allowed here? Can they be modeled in swagger?
checked with backend team, they said it was a work around to keep the sdk compatible because backend returns more properties as time goes.
There was a problem hiding this comment.
If that is the case, then why are the body parameters not modeled in this swagger file?
Hi @anthony-c-martin , I am sorry for giving a wrong reason for why it it post.
I checked with backend team, they said it is a action instead of simply get resource, the action need to be audited and loged. So it is Post instead of Get. Thanks
| } | ||
| } | ||
| }, | ||
| "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Synapse/workspaces/{workspaceName}/integrationRuntimes/{integrationRuntimeName}/nodes/{nodeName}/ipAddress": { |
There was a problem hiding this comment.
Please use a verb here - e.g getIpAddress rather than just ipAddress
There was a problem hiding this comment.
Please use a verb here - e.g
getIpAddressrather than justipAddress
Hi anthony, change api needs backend team support. The backend just use ipAddress.
Please wait me for checking this with the backend team
There was a problem hiding this comment.
Please use a verb here - e.g
getIpAddressrather than justipAddress
Hi @anthony-c-martin I understand your point and I agree with you. But the datafactory is an existing service, synapse reused their some functionality, backend team won't change the api path because the effort is large. Can we ignore this?
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
ARM team has reviewed integrationRuntime.json and related example in https://github.com/Azure/azure-rest-api-specs-pr/pull/1024
Hope this information can reduce ARM review time.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.