create_datasource_asset_comment

DatasourcesApi.create_datasource_asset_comment(role_id, datasource_id, asset_id, asset_comment_input, content_type=None, _request_timeout=None, _request_auth=None, _content_type=None, _headers=None, _host_index=0)

Add a comment to an asset

Adds a comment to an asset (edit access on the datasource required). For internal amorphic assets, the caller must also have at least read access on the underlying asset. Request body must include Type and Description. Description max length is 1000 characters. Response includes Message and CommentId (CommentTime timestamp).

Parameters:

  • role_id (str) – (required)

  • datasource_id (str) – (required)

  • asset_id (str) – (required)

  • asset_comment_input (AssetCommentInput) – (required)

  • content_type (str)

  • _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:

AssetCommentCreateResponse

Returns:

Returns the result object.

Request and Response Examples

HTTP: POST /datasources/{datasource_id}/assets/{asset_id}/comments

Success (HTTP 200)

Successfully added the comment to the asset

Errors

HTTP 400

Invalid input for adding the comment to the asset

HTTP 500

Something went wrong at backend