Retrieve Data Masking Scenario Lists via DsgSceneQuerySceneListByName - DataWorks

Call the DsgSceneQuerySceneListByName API to retrieve a list of data masking scenarios.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

dataworks:DsgSceneQuerySceneListByName

list

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
SceneName	string	No	The keyword for a fuzzy search of data masking scenario names.	dev_

Response elements

Element	Type	Description	Example
	object	OpenApiResultModel<List>
Success	boolean	Indicates whether the request was successful. Valid values: `true`: The request was successful. `false`: The request failed.	true
ErrorCode	string	The error code.	1029030003
ErrorMessage	string	The error message.	param error
HttpStatusCode	integer	The HTTP status code.	400
Data	array<object>	The list of data masking scenarios.
	array<object>	The details of a data masking scenario.
Id	integer	The ID of the data masking scenario.	123
SceneCode	string	The code for the level-1 scenario. Valid values: Data masking in Data Map and DataStudio: `dataworks_display_desense_code` Data masking at the MaxCompute engine layer: `maxcompute_desense_code` Data masking at the MaxCompute engine layer (new): `maxcompute_new_desense_code` Data masking at the Hologres engine layer: `hologres_display_desense_code` Static data masking in Data Integration: `dataworks_data_integration_desense_code` Data masking in Data Analysis: `dataworks_analysis_desense_code`	dataworks_display_desense_code
Desc	string	The description of the data masking scenario.	Test scenarios
SceneName	string	The name of the data masking scenario.	test_scene
UserGroups	string	The user groups to which the data masking scenario applies. Multiple user group names are separated by a comma (,).	user1,user2
SceneLevel	integer	The level of the data masking scenario. Valid values: `0`: level-1 scenario `1`: level-2 scenario	1
Projects	array<object>	The engine instances to which the data masking scenario applies.
	object	An engine instance to which the data masking scenario applies.
DbType	string	The engine type. Valid values: MaxCompute: `ODPS.ODPS` Hologres: `HOLO.POSTGRES` E-MapReduce (EMR): `EMR`	ODPS.ODPS
ProjectName	string	The name of the engine instance.	dev_project
ClusterId	string	The ID of the E-MapReduce (EMR) cluster. This parameter is returned only if the `DbType` is `EMR`.	c-123456
Children	array	The nested data masking scenarios.
	any	A nested (level-2) data masking scenario. The parameters for a nested scenario are the same as those for its parent.	$ref
scenceDbType	string
RequestId	string	The ID of the request. You can use this ID to troubleshoot issues.	102400001

Examples

Success response

JSON format

{
  "Success": true,
  "ErrorCode": "1029030003",
  "ErrorMessage": "param error",
  "HttpStatusCode": 400,
  "Data": [
    {
      "Id": 123,
      "SceneCode": "dataworks_display_desense_code",
      "Desc": "Test scenarios",
      "SceneName": "test_scene",
      "UserGroups": "user1,user2",
      "SceneLevel": 1,
      "Projects": [
        {
          "DbType": "ODPS.ODPS",
          "ProjectName": "dev_project",
          "ClusterId": "c-123456"
        }
      ],
      "Children": [
        "$ref"
      ],
      "scenceDbType": ""
    }
  ],
  "RequestId": "102400001"
}

Error codes

HTTP status code	Error code	Error message	Description
400	DESENSSCENE.ID.ERROR	The desensitization scenario ID does not match or does not exist with the tenant.	The scenario ID does not exist or does not belong to the tenant.
400	DESENSSCENE.IDLEVEL.ERROR	The desensitization scenario is not a secondary scenario.
400	DESENSSCENE.PROJECT.ERROR	The project space does not exist.
400	DESENSSCENE.SIZE.ERROR	The number of desens scene exceeds the limit.	Number of desensitization scenarios chao xian
400	DESENSSCENE.UESRGROUP.ERROR	The user group ID does not match the tenant or does not exist.	The user group ID does not exist or does not belong to the tenant.
400	PARAMS.ERROR	param error.
500	UNKNOWN.ERROR	unknown error.	Unknown error.
403	PERMISSION.DENIED.ERROR	Permission denied	Insufficient permissions.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.