Obtaining the Trigger List of a Specific Image Repository
Function
Obtain the trigger list of a specific image repository.
URI
GET /v2/manage/namespaces/{namespace}/repos/{repository}/triggers
Table 1 describes the parameters.
Request
- Request parameters
Table 2 Request header parameters Parameter
Mandatory
Type
Description
Content-Type
Yes
String
Message body type (format). The value can be application/json or charset=utf-8 application/json.
The default value is application/json.
X-Auth-Token
Yes
String
User token.
The token can be obtained by calling an IAM API. The value of X-Subject-Token in the response header is the user token.
- Example request
GET https://{Endpoint}/v2/manage/namespaces/group/repos/busybox/triggers
Response
- Response parameters
Status code: 200
Table 3 Response body parameter description Parameter
Type
Description
[Array element]
Array of objects
Trigger list
Table 4 [Array element] Parameter
Type
Description
action
String
Action to trigger. The value is update.
app_type
String
Application type. The value can be deployments or statefulsets.
application
String
Application name.
cluster_id
String
Cluster ID. If trigger_mode is set to cci, leave this parameter blank.
cluster_name
String
Cluster name. If trigger_mode is set to cci, leave this parameter blank.
cluster_ns
String
Namespace where the application is located.
condition
String
Trigger condition.
- When trigger_type is set to all, set this parameter to .*.
- When trigger_type is set to tag, set this parameter to specific image tags separated by semicolons (;).
- When trigger_type is set to regular, set this parameter to a regular expression.
container
String
Name of the container to be updated. By default, all containers using this image are updated.
created_at
String
Creation time.
creator_name
String
Creator.
enable
String
Whether to enable the trigger.
name
String
Trigger name.
trigger_history
Array of objects
(Reserved field) This parameter is not in use.
trigger_mode
String
Trigger type. The value can be cce or cci.
trigger_type
String
Trigger condition. The value can be all (all tags), tag (specific tag), or regular (tags matching regular expression).
Table 5 trigger_history parameter description Parameter
Type
Description
action
String
Action to trigger. The value is update.
app_type
String
Application type. The value can be deployments or statefulsets.
application
String
Application name.
cluster_id
String
Cluster ID. If trigger_mode is set to cci, leave this parameter blank.
cluster_name
String
Cluster name. If trigger_mode is set to cci, leave this parameter blank.
cluster_ns
String
Namespace where the application is located.
condition
String
Trigger condition.
- When trigger_type is set to all, set this parameter to .*.
- When trigger_type is set to tag, set this parameter to specific image tags separated by semicolons (;).
- When trigger_type is set to regular, set this parameter to a regular expression.
container
String
Name of the container to be updated. By default, all containers using this image are updated.
created_at
String
Creation time.
creator_name
String
Creator.
detail
String
Details.
result
String
Update result. The value can be success or failed.
tag
String
Triggered tag.
- Example response
The trigger list is returned successfully.
[ { "action": "update", "app_type": "deployments", "application": "abcde", "cluster_id": "******************", "cluster_name": "test123", "cluster_ns": "default", "condition": ".*", "container": "", "created_at": "2020-04-16T02:04:55.922236Z", "creator_name": "************", "enable": "true", "name": "test1", "trigger_history": null, "trigger_mode": "cce", "trigger_type": "all" } ]
Status Code
Status Code |
Description |
---|---|
200 |
Request successful. |
400 |
Request error. |
401 |
Authentication failed. |
404 |
The organization does not exist. |
500 |
Failed to complete the request because of an internal service error. |
Error Codes
For details, see Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot