Tencent Container Registry (TCR) allows users to configure and use the flexible trigger feature. By configuring a proper trigger in an instance, you can quickly integrate existing R&D processes and CI/CD platforms and implement container DevOps scenarios such as image updates that automatically trigger application deployment.
The trigger feature allows users to create custom trigger rules and view triggering logs. Trigger actions support the push, pull, and deletion of container images and Helm Charts. Triggering rules support flexible regular expression filtering and regular filtering based on specified namespaces in an instance and configured image repositories and tags. This allows the trigger to be triggered by only certain repositories or image tags that use special naming formats. The custom Header feature allows users to configure the Header for accessing the target URL in the Key:Value
format, which is applicable to authentication and other scenarios.
Before creating and managing a trigger in a TCR Enterprise Edition instance, complete the following tasks:
-
, .
, and _
). It must start with a letter or number. In this document, webhook-demo
is used as an example.Note:
For a regular expression rule, you can enter rules such as
nginx-*
,{repo1,repo2}
, where:
*
: matches any field that does not contain '/'.**
: matches any field that contains '/'.?
: matches any non-'/' character.{option 1, option 2,...}
: indicates the simultaneously matching of multiple options.
Authentication: xxxxxxx
.After a trigger rule is created, you can view the trigger rule on the "Trigger" page. Then, you can perform the following operations to manage trigger rules. See the figure below:
You can click the name of a specific trigger rule or click Triggering Log to the right of the trigger rule name to view the triggering log of the rule. See the figure below:
The log contains the following information:
When users perform a relevant action on resources that meet a trigger rule, for example, pushing new images to the specified image repository, the relevant trigger is triggered and sends an HTTP POST request to the URL configured in the rule. The request body contains the trigger action and repository path. The following is the resolved information of a sample request body after the trigger is triggered by image push. This sample is for reference in Webhook server development.
{
"type": "pushImage",
"occur_at": 1589106605,
"event_data": {
"resources": [
{
"digest": "sha256:89a42c3ba15f09a3fbe39856bddacdf9e94cd03df7403cad4fc105xxxx268fc9",
"tag": "v1.10.0",
"resource_url": "xxx-bj.tencentcloudcr.com/public/nginx:v1.10.0"
}
],
"repository": {
"date_created": 1587119137,
"name": "nginx",
"namespace": "public",
"repo_full_name": "public/nginx",
"repo_type": "public"
}
},
"operator": "332133xxxx"
}
Was this page helpful?