External-Mirrors/awx
2
0
Fork 0
mirror of https://github.com/ansible/awx.git synced 2026-02-01 01:28:09 -03:30
Code Issues Packages Projects Releases Wiki Activity

Add Rocket.Chat notification type

Browse Source 
Summary: Add Rocket.Chat notification type
Issue type: Feature Pull Request
Component: Notifications

Signed-off-by: Jeandre Le Roux <theblazehen@theblazehen.com>
This commit is contained in:
Jeandre Le Roux
2018-03-21 10:02:50 +02:00
parent e58038b056
commit fd12c44ada
5 changed files with 110 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/notification_system.md
View File

@@ -36,6 +36,7 @@ The currently defined Notification Types are:
* Slack
* Hipchat
* Mattermost
* Rocket.Chat
* Pagerduty
* Twilio
* IRC
@@ -126,6 +127,26 @@ In order to enable these settings in Mattermost:
* Utilize an existing Mattermost installation or use their docker container here: `docker run --name mattermost-preview -d --publish 8065:8065 mattermost/mattermost-preview`
* Turn on Incoming Webhooks and optionally allow Integrations to override usernames and icons in the System Console.
## Rocket.Chat
The Rocket.Chat notification integration uses Incoming Webhooks. A password is not required because the webhook URL itself is the secret. An integration must be created in the Administration section of the Rocket.Chat settings.
The following fields are available for the Rocket.Chat notification type:
* `url`: The incoming webhook URL that was configured in Rocket.Chat. Notifications will use this URL to POST.
* `username`: Optional. Change the displayed username from Rocket Cat to specified username
* `icon_url`: Optional. A URL pointing to an icon to use for the notification.
### Testing considerations
* Make sure that all options behave as expected
* Test that all notification options are obeyed
### Test Service
* Utilize an existing Rocket.Chat installation or use their docker containers from https://rocket.chat/docs/installation/docker-containers/
* Create an Incoming Webhook in the Integrations section of the Administration settings
## Pagerduty
Pager duty is a fairly straightforward integration. The user will create an API Key in the pagerduty system (this will be the token that is given to Tower) and then create a "Service" which will provide an "Integration Key" that will be given to Tower also. The other options of note are: