Added support for Jira, Pagerduty and Increased Slack to include webooks and custom fields #149
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've created some Custom alert_action to add additional support for pagerduty and Jira.
I have a feeling these applications are popular enough that this feature would benefit the wider contentctl community.
I've attached some images if you'd like to see a POC.
PagerDuty
Jira
This code can be tested by adding the alert_action key in the yaml file. See below
alert_action:
jira:
account: JiraServiceAccount
jira_attachment: enabled_json
jira_dedup: enabled
jira_dedup_content: your condition
jira_description: your description
jira_issue_type: Alert
jira_priority: Three
jira_priority_dynamic: your dynamic priority
jira_project: your project
jira_summary: your summary
pagerduty:
pagerduty_description: your description
integration_url_override: optional pagerduty url
slack:
channel: your channel
message: your message
fields: outputted fields
webhook_url: webhookurl
This is my first PR with contentctl so let me know what else i need to add or supply.