community.general.pagerduty_change – Track a code or infrastructure change as a PagerDuty change event¶
Note
This plugin is part of the community.general collection (version 2.5.1).
To install it use: ansible-galaxy collection install community.general
.
To use it in a playbook, specify: community.general.pagerduty_change
.
New in version 1.3.0: of community.general
Synopsis¶
This module will let you create a PagerDuty change event each time the module is run.
This is not an idempotent action and a new change event will be created each time it is run.
Requirements¶
The below requirements are needed on the host that executes this module.
PagerDuty integration key
Parameters¶
Notes¶
Note
Supports
check_mode
. Note that check mode simply does nothing except returningchanged=true
in case the url seems to be correct.
Examples¶
- name: Track the deployment as a PagerDuty change event
community.general.pagerduty_change:
integration_key: abc123abc123abc123abc123abc123ab
summary: The application was deployed
- name: Track the deployment as a PagerDuty change event with more details
community.general.pagerduty_change:
integration_key: abc123abc123abc123abc123abc123ab
summary: The application was deployed
source: Ansible Deploy
user: ansible
repo: github.com/ansible/ansible
revision: '4.2'
environment: production
link_url: https://github.com/ansible-collections/community.general/pull/1269
link_text: View changes on GitHub
Authors¶
Adam Vaughan (@adamvaughan)