Help Center/ Workspace/ API Reference/ Workspace APIs/ Tenant Configuration/ Modifying a Custom Tenant Configuration
Updated on 2025-07-14 GMT+08:00

Modifying a Custom Tenant Configuration

Function

Modifies a custom tenant configuration.

Debugging

You can debug this API through automatic authentication in API Explorer or use the SDK sample code generated by API Explorer.

URI

PUT /v2/{project_id}/tenant-configs

Table 1 Path Parameters

Parameter

Mandatory

Type

Description

project_id

Yes

String

Project ID.

Request Parameters

Table 2 Request header parameters

Parameter

Mandatory

Type

Description

X-Auth-Token

No

String

User token.

It can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token.

Content-Type

Yes

String

MIME type of the request body.

Table 3 Request body parameters

Parameter

Mandatory

Type

Description

function_config

No

FunctionConfig object

Custom tenant configuration.

Table 4 FunctionConfig

Parameter

Mandatory

Type

Description

id

No

String

Function configuration ID.

name

No

String

Function configuration name.

status

No

String

Status of the function configuration switch. Options: - ON: enabled; OFF: disabled

values

No

Array of MapObject objects

Configuration item list, in key-value pair format.

Table 5 MapObject

Parameter

Mandatory

Type

Description

key

No

String

Key of a configuration item.

value

No

String

Value of a configuration item.

Response Parameters

Status code: 204

Normal.

Status code: 400

Table 6 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

encoded_authorization_message

String

Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason.

Status code: 401

Table 7 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

encoded_authorization_message

String

Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason.

Status code: 403

Table 8 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

encoded_authorization_message

String

Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason.

Status code: 404

Table 9 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

encoded_authorization_message

String

Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason.

Status code: 500

Table 10 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

encoded_authorization_message

String

Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason.

Example Requests

{
  "function_config" : {
    "id" : "xxx-xxx-xxx",
    "name" : "user_prefix",
    "status" : "ON",
    "values" : [ {
      "key" : "prefix",
      "value" : "test"
    } ]
  }
}

Example Responses

None

Status Codes

Status Code

Description

204

Normal.

400

The request cannot be understood by the server due to malformed syntax.

401

Authentication failed.

403

No operation permissions.

404

No resources found.

500

An internal service error occurred. For details, see the error code description.

Error Codes

See Error Codes.