delete_datasource_asset_comment¶
- DatasourcesApi.delete_datasource_asset_comment(datasource_id, asset_id, comment_id, role_id, _request_timeout=None, _request_auth=None, _content_type=None, _headers=None, _host_index=0)¶
Delete the comment on an asset
Deletes a comment on an asset (edit access on the datasource required). For internal amorphic assets, asset-level permission is also checked. The caller must be the comment author, or an owner/editor of the asset. comment_id is the CommentTime value returned as CommentId on create (URL-encoded values are accepted). Response is Message only.
- Parameters:
datasource_id (str) – (required)
asset_id (str) – (required)
comment_id (str) – Comment identifier (CommentTime timestamp from create response). (required)
role_id (str) – (required)
_request_timeout (int, tuple(int, int), optional) – timeout setting for this request. If one number provided, it will be total request timeout. It can also be a pair (tuple) of (connection, read) timeouts.
_request_auth (dict, optional) – set to override the auth_settings for an a single request; this effectively ignores the authentication in the spec for a single request.
_content_type (str, Optional) – force content-type for the request.
_headers (dict, optional) – set to override the headers for a single request; this effectively ignores the headers in the spec for a single request.
_host_index (int, optional) – set to override the host_index for a single request; this effectively ignores the host_index in the spec for a single request.
- Return type:
- Returns:
Returns the result object.
Request and Response Examples¶
HTTP: DELETE /datasources/{datasource_id}/assets/{asset_id}/comments/{comment_id}
Success (HTTP 200)¶
Comment deleted successfully
Errors¶
HTTP 400
Invalid comment id, missing parameters, or unauthorized delete
HTTP 500
Something went wrong at backend