-
Notifications
You must be signed in to change notification settings - Fork 5.6k
add linked workspace endpoints(Ready for review) #8918
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
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-net
|
azure-cli-extensions
|
azure-sdk-for-java
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-python
- Breaking Change detected in SDK
|
azure-sdk-for-js
|
azure-sdk-for-go
|
|
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 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). |
|
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). |
|
Though we introduced new APIs and properties in this PR, we don't want to bump the api-Version right now, because:
|
...rce-manager/Microsoft.MachineLearningServices/stable/2020-03-01/machineLearningServices.json
Show resolved
Hide resolved
...rce-manager/Microsoft.MachineLearningServices/stable/2020-03-01/machineLearningServices.json
Show resolved
Hide resolved
| } | ||
| } | ||
| }, | ||
| "post": { |
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.
post [](start = 7, length = 4)
Resource updates should be done with PUT not POST as per the RPC. (https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/resource-api-reference.md)
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.
again, that's because LinkedWorkspace is not a resource, yet.
...rce-manager/Microsoft.MachineLearningServices/stable/2020-03-01/machineLearningServices.json
Outdated
Show resolved
Hide resolved
| } | ||
| } | ||
| }, | ||
| "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/Microsoft.MachineLearningServices/workspaces/{workspaceName}/delinkWorkspace/{linkName}": { |
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.
delinkWorkspace [](start = 133, length = 15)
Are you introducing a separate nested resource type for de-linked workspaces? Did you mean to create a delink POST action on a linked workspace instead?
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.
User can link multiple LinkedWorkspace to Workspace, here is to delink one of them, i.e. delete a LinkedWorkspace. If DELETE is not reserved for resource, I will use DELETE .../linkedWorkspace/{linkName} here. And POST .../linkedWorkspace/{linkName} is used by the update, so I use .../delinkWorkspace/{linkName} here for delete.
| "workspaceName": "linkedWorkspace-1234", | ||
| "userAssignedIdentityResourceId": "/subscriptions/00000000-1111-2222-3333-444444444444/resourceGroups/resourceGroup-4321/providers/Microsoft.ManagedIdentity/userAssignedIdentities/uai123", | ||
| "resourceId": "/subscriptions/00000000-1111-2222-3333-444444444444/resourceGroups/linkRg-123/providers/Microsoft.Synapse/workspaces/linkedWorkspace-1234" | ||
| }, |
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 is not an RPC-compliant resource payload. You should have a top level id, 'name, type property and all the resource properties should go into the properties property. Please take a look at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/resource-api-reference.md#resource-api-reference.
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.
LinkedWorkspace is not yet a resource.
| "200": { | ||
| "description": "Successfully deleted the linked workspace." | ||
| }, | ||
| "204": { |
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.
I suppose 204 is ok to be kept?
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.