Help Center/ SecMaster/ API Reference/ SecMaster APIs (V1)/ Component Management/ Obtaining the Configuration Data of a Historical Component Version
Updated on 2025-12-18 GMT+08:00

Obtaining the Configuration Data of a Historical Component Version

Function

This API is used to obtain the configuration data of historical component versions.

Calling Method

For details, see Calling APIs.

URI

GET /v1/{project_id}/workspaces/{workspace_id}/components/{component_id}/configurations/versions

Table 1 Path Parameters

Parameter

Mandatory

Type

Description

project_id

Yes

String

Definition

Project ID, which is used to specify the project that a resource belongs to. You can query the resources of a project by project ID. You can obtain the project ID from the API or console. Obtaining the Project ID

Constraints

N/A

Value Range

N/A

Default value

N/A

workspace_id

Yes

String

Workspace ID.

component_id

Yes

String

Component ID.

Table 2 Query Parameters

Parameter

Mandatory

Type

Description

offset

No

Long

Page number.

limit

No

Long

Number of records on each page.

sort_key

No

String

Sorting field.

sort_dir

No

String

Sorting order.

Request Parameters

Table 3 Request header parameters

Parameter

Mandatory

Type

Description

X-Auth-Token

Yes

String

Definition

User token. You can obtain it by calling the IAM API for obtaining a user token. The user token is the value of X-Subject-Token in the response header. Obtaining a User Token

Constraints

N/A

Range

N/A

Default Value

N/A

Response Parameters

Status code: 200

Table 4 Response body parameters

Parameter

Type

Description

count

Long

Total number of lists.

records

Array of ComponentConfigurationInfo objects

Node parameter.

Table 5 ComponentConfigurationInfo

Parameter

Type

Description

configuration_status

String

Node configuration status. The options are as follows: UN_SAVED: The node has not been saved; SAVE_AND_UN_DEPLOY: The node has been saved but not deployed; DEPLOYING: The not is being deployed.

MOVE_AND_UN_DEPLOY: removed and not applied; FAIL_DEPLOY: deployment failed; DEPLOYED: deployed

list

Array of ComponentConfigurationParamVo objects

File parameter information.

node_id

String

Node ID.

node_name

String

Node name.

node_status

String

Node status. NORMAL: normal; ANOMALIES: abnormal; FAULTS: faulty; LOST_CONTACT: disconnected.

specification

String

Node specifications.

Table 6 ComponentConfigurationParamVo

Parameter

Type

Description

configuration_id

String

id

file_name

String

File name.

file_type

String

File type.

node_id

String

Node ID.

param

String

Parameter.

type

String

Type.

version

String

Version.

Status code: 400

Table 7 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error message.

Example Requests

None

Example Responses

None

Status Codes

Status Code

Description

200

Successful.

400

Error response.

Error Codes

See Error Codes.