- What's new
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Introduction
- Permissions Management
- Basics of the Container Engine
-
Image Management
- Uploading an Image Through a Container Engine Client (Recommended)
- Obtaining a Long-Term Valid Login Command
- Uploading an Image Through SWR Console
- Pulling an Image
- Setting Image Attributes
- Sharing a Private Image
- Adding a Trigger
- Adding an Image Retention Policy
- Configuring Automatic Image Synchronization Between Regions
- Image Center
- Organization Management
- User Permissions
- Auditing
- Change History
- Best Practices
-
API Reference
- Before You Start
- Calling APIs
- API Overview
-
API
- Organization Management
- Managing Image Repositories
- Image Tag Management
- Shared Account Management
- API Version
- Organization Permission Management
- Image Permission Management
- Image Synchronization Management
- Trigger Management
- Image Retention Policy Management
- Temporary Login Command
- Quota Management
- Other
- Example Applications
- Appendixes
- SDK Reference
-
FAQs
- General FAQs
- Login Issues
- Synchronizing Images
- Pushing an Image
- Pulling an Image
-
Troubleshooting
- Why Does the Login Command Fail to Be Executed?
- Why Does an Image Fail to Be Pushed Through a Container Engine Client?
- Why Does an Image Fail to Be Uploaded Through SWR Console?
- Why Does the docker pull Command Fail to Be Executed?
- What Should I Do If Images Cannot Be Downloaded from Private Networks?
- What Do I Do If an Error Occurs When I Call an API?
-
Other FAQs
- Why Does a CCE Workload Cannot Pull an Image from SWR and a Message "Not Logged In" Is Displayed?
- How Many Tenants Can I Share an SWR Private Image With?
- Why Is an Image Pushed Using a Container Engine Client to SWR Different in Size From One Uploaded Through the SWR Console?
- Can I Pull Images on the SWR Console to a Local PC?
- Videos
- Glossary
-
More Documents
- User Guide
- API Reference
- User Guide (Paris Regions)
- API Reference (Paris Regions)
- User Guide (Kuala Lumpur Region)
- API Reference (Kuala Lumpur Region)
-
User Guide (Ankara Region)
- Service Overview
- Overview
- Permissions Management
- Basics of Docker
-
Image Management
- Pushing an Image Through a Container Engine Client
- Obtaining a Long-Term Valid Docker Login Command
- Obtaining a Long-Term Valid containerd Pull/Push Command
- Uploading an Image Through the SWR Console
- Pulling an Image
- Setting Image Attributes
- Sharing Private Images
- Adding a Trigger
- Adding an Image Retention Policy
- Organization Management
- User Permissions
- FAQs
-
API Reference (Ankara Region)
- Before You Start
- API Overview
- Calling APIs
- API
- Appendixes
- Permissions and Supported Actions
- General Reference
Copied.
Obtaining Information About a Trigger
Function
Obtain information about a trigger.
URI
GET /v2/manage/namespaces/{namespace}/repos/{repository}/triggers/{trigger}
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/test
Response
- Response parameters
Table 3 Response body parameter description Parameter
Type
Description
action
String
Action to trigger. The value can be 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
Trigger history.
trigger_mode
String
Trigger type. The value can be cce or cci.
trigger_type
String
Trigger condition. The value can be all, tag, or regular.
Table 4 Parameter description Parameter
Type
Description
action
String
Action to trigger. The value can be update.
app_type
String
Application type. The value can be deployments or statefulsets.
application
String
Application name.
cluster_id
String
(Reserved field) Cluster ID.
cluster_name
String
(Reserved field) Cluster name.
cluster_ns
String
(Reserved field) 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
Image tag that triggers the update.
- Example response
{ "action": "update", "app_type": "deployments", "application": "cci-deployment-20204161", "cluster_id": "", "cluster_name": "", "cluster_ns": "cci-namespace-21539491", "condition": ".*", "container": "", "created_at": "2020-04-16T01:35:08.639589Z", "creator_name": "paas_swr_z00232859", "enable": "true", "name": "test", "trigger_history": [ { "action": "update", "app_type": "deployments", "application": "cci-deployment-20204161", "cluster_id": "", "cluster_name": "", "cluster_ns": "", "condition": ".*", "container": "", "created_at": "2020-04-16T01:36:36.155119Z", "creator_name": "************", "detail": "xxxxxxxxxxxxxx", "result": "failed", "tag": "test" } ], "trigger_mode": "cci", "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