AWS CodeCommit source
This event source captures notifications from an AWS CodeCommit repository whenever a specific action, such as a new commit or the creation of a pull request, happens in this repository.
With tmctl
:
tmctl create source awscodecommit --arn <arn> --branch <branch> --eventTypes pull_request --auth.credentials.accessKeyID <keyID> --auth.credentials.secretAccessKey <key>
On Kubernetes:
apiVersion: sources.triggermesh.io/v1alpha1
kind: AWSCodeCommitSource
metadata:
name: sample
spec:
arn: arn:aws:codecommit:us-west-2:123456789012:triggermeshtest
branch: master
eventTypes:
- push
- pull_request
auth:
credentials:
accessKeyID:
valueFromSecret:
name: awscreds
key: aws_access_key_id
secretAccessKey:
valueFromSecret:
name: awscreds
key: aws_secret_access_key
sink:
ref:
apiVersion: eventing.triggermesh.io/v1alpha1
kind: RedisBroker
name: triggermesh
Alternatively you can use an IAM role for authentication instead of an access key and secret, for Amazon EKS only:
To setup an IAM role for service accounts, please refer to the official AWS documentation.
The parameters include the following:
Events produced have the following attributes:
- types
com.amazon.codecommit.push
com.amazon.codecommit.pull_request
- Schema of the
data
attribute:
See the Kubernetes object reference for more details.
Prerequisite(s)
- CodeCommit Repository and Branch
- Amazon Resource Name (ARN)
- API Credentials
CodeCommit Repository and Branch
If you don't already have an AWS CodeCommit repository, create one by following the instructions at Create an AWS CodeCommit repository. The repository should contain at least one branch. To create one, follow the instructions at Create a branch in AWS CodeCommit.
Amazon Resource Name (ARN)
A fully qualified ARN is required to uniquely identify the AWS CodeCommit repository.
The easiest way to obtain the ARN of a CodeCommit repository is by using the AWS CLI. The following command
retrieves the information of a repository called triggermeshtest
in the us-west-2
region:
$ aws codecommit get-repository --repository-name triggermeshtest --region us-west-2
{
"repositoryMetadata": {
"accountId": "123456789012",
"repositoryId": "510acd3d-b96d-473c-bbe4-a8c6799d02a9",
"repositoryName": "triggermeshtest",
"defaultBranch": "main",
"lastModifiedDate": "2020-07-20T20:54:27.806000+02:00",
"creationDate": "2020-07-20T20:49:12.324000+02:00",
"cloneUrlHttp": "https://git-codecommit.eu-central-1.amazonaws.com/v1/repos/triggermeshtest",
"cloneUrlSsh": "ssh://git-codecommit.eu-central-1.amazonaws.com/v1/repos/triggermeshtest",
"Arn": "arn:aws:codecommit:eu-central-1:123456789012:triggermeshtest"
}
}
If you don't have the AWS CLI installed on your workstation, you can use the template below to compose a fully qualified ARN of a CodeCommit repository.
API Credentials
The TriggerMesh event source for Amazon CodeCommit authenticates calls to the AWS API using AWS Access Keys. The page Understanding and getting your AWS credentials contains instructions to create access keys when signed-in either as the root user or as an IAM user. Take note of the Access Key ID and Secret Access Key, they will be used to create an instance of the event source.
It is considered a good practice to create dedicated users with restricted privileges in order to programmatically access AWS services. Permissions can be added or revoked granularly for a given IAM user by attaching IAM Policies to it.
As an example, the following policy contains only the permissions required by the TriggerMesh AWS CodeCommit event source to operate: