-
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
OperationalInsights: DataCollectorLogs new api support. #10365
Conversation
[Staging] Swagger Validation Report
️✔️ |
Rule | Message |
---|---|
R4011 - DeleteOperationResponses |
The delete operation is defined without a 200 or 204 error response implementation,please add it.' New: Microsoft.OperationalInsights/preview/2020-03-01-preview/DataCollectorLogs.json#L76 |
The child tracked resource, 'gateways' with immediate parent 'Workspace', must have a list by immediate parent operation. New: Microsoft.OperationalInsights/preview/2020-03-01-preview/Tables.json#L180 |
|
The child tracked resource, 'operations' with immediate parent 'Workspace', must have a list by immediate parent operation. New: Microsoft.OperationalInsights/preview/2020-03-01-preview/Tables.json#L180 |
️️✔️
Avocado [Detail]
️✔️
Validation passes for Avocado.
️️✔️
ModelValidation [Detail]
️✔️
Validation passes for ModelValidation.
️️✔️
SemanticValidation [Detail]
️✔️
Validation passes for SemanticValidation.
Azure Pipelines successfully started running 1 pipeline(s). |
Can one of the admins verify this patch? |
azure-sdk-for-net - Release
|
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 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-sdk-for-js - Release
|
azure-sdk-for-python - Release
|
azure-sdk-for-java - Release
|
azure-sdk-for-go - 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
|
Azure Pipelines successfully started running 1 pipeline(s). |
...urce-manager/Microsoft.OperationalInsights/preview/2020-03-01-preview/DataCollectorLogs.json
Outdated
Show resolved
Hide resolved
...urce-manager/Microsoft.OperationalInsights/preview/2020-03-01-preview/DataCollectorLogs.json
Outdated
Show resolved
Hide resolved
...urce-manager/Microsoft.OperationalInsights/preview/2020-03-01-preview/DataCollectorLogs.json
Outdated
Show resolved
Hide resolved
...urce-manager/Microsoft.OperationalInsights/preview/2020-03-01-preview/DataCollectorLogs.json
Outdated
Show resolved
Hide resolved
Azure Pipelines successfully started running 1 pipeline(s). |
...urce-manager/Microsoft.OperationalInsights/preview/2020-03-01-preview/DataCollectorLogs.json
Outdated
Show resolved
Hide resolved
Azure Pipelines successfully started running 1 pipeline(s). |
...urce-manager/Microsoft.OperationalInsights/preview/2020-03-01-preview/DataCollectorLogs.json
Outdated
Show resolved
Hide resolved
...urce-manager/Microsoft.OperationalInsights/preview/2020-03-01-preview/DataCollectorLogs.json
Show resolved
Hide resolved
...urce-manager/Microsoft.OperationalInsights/preview/2020-03-01-preview/DataCollectorLogs.json
Show resolved
Hide resolved
...urce-manager/Microsoft.OperationalInsights/preview/2020-03-01-preview/DataCollectorLogs.json
Show resolved
Hide resolved
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @myronfanqiu, |
@Dudi119 We need ARM's review as well. |
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.
@Dudi119 few comments
} | ||
], | ||
"responses": { | ||
"200": { |
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.
what is the response of this post action?
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.
please add the response schema.
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.
no schema, just 200 since its basically a delete.
} | ||
} | ||
}, | ||
"get": { |
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.
how is the POST different from this GET? the API signature is same.
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.
so the scenario is user lists the tables and then you want to give them the option to delete them. In that case, your POST should be changed to a DELETE, and they can provide the tableName that they want to delete. Much cleaner approach. POST for delete is ugly.
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.
we do not support full CRUD, is it fine if i will supply delete and get and no put? this is why we used post 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.
yes, it will be ok to have GET and DELETE
} | ||
}, | ||
"paths": { | ||
"/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/{workspaceName}/dataCollectorLogs": { |
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.
From description it seems like this POST action is used to delete a log table. what is the need to expose deletion operation through the control plane on something (tables) which is not exposed on the control plane. Its wierd and can cause of sorts of issues like permission check, inconsistent state/confusion for customer where i am assuming same thing can be from the dataplane api as well etc.
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.
and if we agree that this is the only way to go about it and its required, i will ask you, at the very least to change the name of this action. This POST action from the name seems very harmless but it ends up deleting something. So name should indicate what this operation does. may be call it deleteDataCollectorLogsTable. But lets answer the above question first.
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.
it all derives from the fact this is not a typical CRUD, so post is multi purpose, in this case being used for delete.
i have no problem changing the post to delete, but there will be no put. is that sounds reasonable?
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, better to switch to GET and DELETE
Azure Pipelines successfully started running 1 pipeline(s). |
azure-resource-manager-schemas - Release
|
Azure Pipelines successfully started running 1 pipeline(s). |
please also add a GET "/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/{workspaceName}/dataCollectorLogs/{tableName} |
SIgning off conditionally assuming the point GET will not be a big deal to add. |
@Dudi119 Hi. Could you please fix one lint error about the delete operation? |
@myronfanqiu, sure, i will review it, i also need to add another point get so a few more things to add. |
Azure Pipelines successfully started running 1 pipeline(s). |
@myronfanqiu, our Delete only returns 200 with no content, we do not supply 204. |
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.