community.general.gitlab_hook module – Manages GitLab project hooks
Note
This module is part of the community.general collection (version 9.4.0).
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install community.general
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: community.general.gitlab_hook
.
Synopsis
Adds, updates and removes project hook
Requirements
The below requirements are needed on the host that executes this module.
python-gitlab python module
requests (Python library https://pypi.org/project/requests/)
Parameters
Parameter |
Comments |
---|---|
GitLab CI job token for logging in. |
|
GitLab OAuth token for logging in. |
|
The password to use for authentication against the API. |
|
GitLab access token with API permissions. |
|
The resolvable endpoint for the API. |
|
The username to use for authentication against the API. |
|
The CA certificates bundle to use to verify GitLab server certificate. |
|
The url that you want GitLab to post to, this is used as the primary key for updates and deletion. |
|
Whether GitLab will do SSL verification when triggering the hook. Choices:
|
|
Trigger hook on issues events. Choices:
|
|
Trigger hook on job events. Choices:
|
|
Trigger hook on merge requests events. Choices:
|
|
Trigger hook on note events or when someone adds a comment. Choices:
|
|
Trigger hook on pipeline events. Choices:
|
|
Id or Full path of the project in the form of group/name. |
|
Trigger hook on push events. Choices:
|
|
Branch name of wildcard to trigger hook on push events Default: |
|
Trigger hook on release events. Choices:
|
|
When When Choices:
|
|
Trigger hook on tag push events. Choices:
|
|
Secret token to validate hook messages at the receiver. If this is present it will always result in a change as it cannot be retrieved from GitLab. Will show up in the X-GitLab-Token HTTP request header. |
|
Whether or not to validate SSL certs when supplying a HTTPS endpoint. Choices:
|
|
Trigger hook on wiki events. Choices:
|
Attributes
Attribute |
Support |
Description |
---|---|---|
Support: full |
Can run in |
|
Support: none |
Will return details on what has changed (or possibly needs changing in |
Examples
- name: "Adding a project hook"
community.general.gitlab_hook:
api_url: https://gitlab.example.com/
api_token: "{{ access_token }}"
project: "my_group/my_project"
hook_url: "https://my-ci-server.example.com/gitlab-hook"
state: present
push_events: true
tag_push_events: true
token: "my-super-secret-token-that-my-ci-server-will-check"
- name: "Delete the previous hook"
community.general.gitlab_hook:
api_url: https://gitlab.example.com/
api_token: "{{ access_token }}"
project: "my_group/my_project"
hook_url: "https://my-ci-server.example.com/gitlab-hook"
state: absent
- name: "Delete a hook by numeric project id"
community.general.gitlab_hook:
api_url: https://gitlab.example.com/
api_token: "{{ access_token }}"
project: 10
hook_url: "https://my-ci-server.example.com/gitlab-hook"
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
the error message returned by the GitLab API Returned: failed Sample: |
|
API object Returned: always |
|
Success or failure message Returned: always Sample: |
|
json parsed response from the server Returned: always |