Updating metadata of a private hook

Function

UpdatePrivateHookMetadata

You can use this API to update the private hook metadata.

Currently, the description, default version and configuration of the private hook can be updated.
If you need to create a new version, please call CreatePrivateHookVersion API.
The update is an incremental update, meaning if a parameter is not provided, the original value will be retained.
If the request does not contain any parameters that need to be updated, error code 400 will be returned. Note: Even if the original value and the target value are the same, it is considered a valid update.
After the update, the update time of the private hook will also be updated.
If both hook_name and hook_id are provided, RFS checks whether they match. If hook name does not match the current private hook ID, error code 400 is returned.

URI

PATCH /v1/private-hooks/{hook_name}/metadata

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
hook_name	Yes	String	Private hook name. The name is unique within its domain (domain_id) and region. It can contain Chinese characters, uppercase and lowercase letters, digits, underscores (_), and hyphens (-). The first character must be a Chinese or English character. It is case sensitive. We recommend users to use a three-part namespace for naming: {custom-hook-name}-{hook application context}-hook.

Request Parameters

**Table 2** Request header parameters
Parameter	Mandatory	Type	Description
Client-Request-Id	Yes	String	Unique request ID. It is specified by a user and is used to locate a request. UUID is recommended.

**Table 3** Request body parameters
Parameter	Mandatory	Type	Description
hook_description	No	String	Description of a private hook. It can be used by customers to identify their own private hooks. You can update the description of the private hook by calling UpdatePrivateHook API.
hook_id	No	String	Unique ID of a private hook. It is an UUID generated by RFS when a private hook is created. Private hook names are unique only at one specific time, so you can create a private hook named helloWorld and another private hook with the same name after deleting the first one. For parallel development in a team, users may want to ensure that the private hook they operate is the one created by themselves, not the one with the same name created by other teammates after deleting the previous one. Therefore, they can use this ID for strong matching. RFS ensures that the ID of each private hook is different and does not change with updates. If the hook_id value is different from the current private hook ID, error code 400 is returned.
default_version	No	String	Private hook default version. The version number follows the Semantic Version and is customized by the user.
configuration	No	configuration object	Private hook configuration. It can specify the target stack where the private hook takes effect and the behavior of the stack after the private hook verification fails. You can use UpdatePrivateHook API to update private hook configuration.

**Table 4** configuration
Parameter	Mandatory	Type	Description
target_stacks	No	String	Specifies the target stack where the private hook takes effect. The value can be NONE or ALL. NONE: Specifies that this private hook will not be applied to any stacks. ALL: Specifies that the private hook will be applied to all stacks under the account.
failure_mode	No	String	Specifies the behavior when the private hook validation fails. Valid values are FAIL or WARN. FAIL: Specifies that if this private hook validation fails, the stack will stop deploying, and the stack status will be updated to DEPLOYMENT_FAILED. WARN: Specifies that if this private hook validation fails, only a warning message will be displayed through the stack events, but it will not affect the deployment of the stack.

Response Parameters

Status code: 400

**Table 5** Response body parameters
Parameter	Type	Description
error_code	String	Response code
error_msg	String	Response message

Status code: 401

**Table 6** Response body parameters
Parameter	Type	Description
error_code	String	Response code
error_msg	String	Response message

Status code: 403

**Table 7** Response body parameters
Parameter	Type	Description
error_code	String	Response code
error_msg	String	Response message

Status code: 404

**Table 8** Response body parameters
Parameter	Type	Description
error_code	String	Response code
error_msg	String	Response message

Status code: 409

**Table 9** Response body parameters
Parameter	Type	Description
error_code	String	Response code
error_msg	String	Response message

Status code: 429

**Table 10** Response body parameters
Parameter	Type	Description
error_code	String	Response code
error_msg	String	Response message

Status code: 500

**Table 11** Response body parameters
Parameter	Type	Description
error_code	String	Response code
error_msg	String	Response message

Example Requests

Update the description of a specified private hook

PATCH https://{endpoint}/v1/private-hooks/my-hello-world-hook-name/metadata

{
  "hook_description" : "my first private hook"
}

Update the default version of a specified private hook

PATCH https://{endpoint}/v1/private-hooks/my-hello-world-hook-name/metadata

{
  "default_version" : "0.0.2"
}

Update the configuration of a specified private hook

PATCH https://{endpoint}/v1/private-hooks/my-hello-world-hook-name/metadata

{
  "configuration" : {
    "target_stacks" : "ALL",
    "failure_mode" : "FAIL"
  }
}

Update the description, default version and configuration of a specified private hook

PATCH https://{endpoint}/v1/private-hooks/my-hello-world-hook-name/metadata

{
  "hook_description" : "my first private hook",
  "default_version" : "0.0.2",
  "configuration" : {
    "target_stacks" : "ALL",
    "failure_mode" : "FAIL"
  }
}

Updates description of the private hook with the hook_id

PATCH https://{endpoint}/v1/private-hooks/my-hello-world-hook-name/metadata

{
  "hook_id" : "77dad9a0-6b11-4bf5-ba62-c7e0029dcb6f",
  "hook_description" : "my first private hook"
}

Example Responses

None

Status Codes

Status Code	Description
204	Private hook metadata updated successfully. No content returned.
400	Invalid request.
401	Authentication failed.
403	The user does not have the permission to call this API.
404	The private hook or default private hook version does not exist.
409	Request conflict. The default version has been deleted. Request conflict. The private hook has been updated.
429	Too frequent requests.
500	Internal server error.