- Fork and clone this repo: https://github.com/diggerhq/gitlab-webhook-lambda.
- If necessary, update the
serverless.ymlfile in the cloned repository. This file contains configuration settings for the Lambda function and can be customized to suit your requirements. - Save the
GITLAB_TOKENto the SSM (Systems Manager) parameter store. You can choose any path for storing the token, but ensure that theserverless.ymlfile is updated accordingly if you deviate from the default path. For example, save theGITLAB_TOKENtossm:/gitlab-dev-webhook-handler/dev/GITLAB_TOKEN. - Do the same for SECRET_TOKEN, update serverless.yml if needed and save token value to ssm parameter (for example ssm:/gitlab-dev-webhook-handler/dev/SECRET_TOKEN)
- Make sure that your AWS credentials are properly configured in the command-line interface (CLI). This ensures that you have the necessary permissions to deploy the Lambda function.
- Run the command
npm run buildin the root directory of the cloned repository. This command will build the necessary artifacts for the Lambda function. - Finally, run the command
npm run deployin the same root directory. This will initiate the deployment process for the Lambda function using the configuration specified in theserverless.ymlfile.
- Group Access Tokens (https://docs.gitlab.com/ee/user/group/settings/group_access_tokens.html) are not supported at the moment, only Project Access Tokens (https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html)
- One Lambda can handle webhooks for multiple GitLab Projects (repos)
- GITLAB_TOKEN is a JSON with a list of maps with project id and token. For example:
[
{"project": "46465722", "token": "glpat-1212232311"},
{"project": "44723537": "token": "glpat-2323232323"}
]
npm run build
serverless deploy
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent