Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update pagerduty_alert module with newest api endpoint and add in params that is newly supported #6151

Closed
1 task done
xshen1 opened this issue Mar 6, 2023 · 3 comments
Closed
1 task done
Labels
feature This issue/PR relates to a feature request has_pr module module monitoring plugins plugin (any type)

Comments

@xshen1
Copy link
Contributor

xshen1 commented Mar 6, 2023

Summary

I am trying to update pagerduty_alert module with the newest api endpoint and add in params that are newly supported. With this improvement, the community and my team will be able to create alerts with different levels of severity, have additional comments in the alert, and have links that are relevant to the alert. Referring to https://developer.pagerduty.com/docs/ZG9jOjExMDI5NTgx-send-an-alert-event

Issue Type

Feature Idea

Component Name

pagerduty_alert

Additional Information

Code of Conduct

  • I agree to follow the Ansible Code of Conduct
@ansibullbot
Copy link
Collaborator

Files identified in the description:

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

@ansibullbot
Copy link
Collaborator

cc @ApsOps
click here for bot help

@ansibullbot ansibullbot added feature This issue/PR relates to a feature request module module monitoring plugins plugin (any type) labels Mar 6, 2023
@felixfontein
Copy link
Collaborator

Should be fixed by #7183.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature This issue/PR relates to a feature request has_pr module module monitoring plugins plugin (any type)
Projects
None yet
Development

No branches or pull requests

3 participants