We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The datadog_downtime module does not currently provide any parameters to choose the value for the mute_first_recovery_notification downtime configuration (https://docs.datadoghq.com/monitors/downtimes/?tab=bymonitorname#disable-first-recovery-notification), which is available in the Datadog API.
datadog_downtime
mute_first_recovery_notification
I think it would be interesting to add it to complete the functional coverage of the Ansible module
Feature Idea
The text was updated successfully, but these errors were encountered:
Files identified in the description:
plugins/modules/datadog_downtime.py
If these files are incorrect, please update the component name section of the description or use the !component bot command.
component name
!component
click here for bot help
Sorry, something went wrong.
cc @DataDog click here for bot help
Have to use v2 datadog api. I'm on it to upgrade the files. Units test OK Sanity test KO
Update datadog downtime module with datadog API v2 (ansible-collectio…
d69f329
…ns#9080)
Successfully merging a pull request may close this issue.
Summary
The
datadog_downtime
module does not currently provide any parameters to choose the value for themute_first_recovery_notification
downtime configuration (https://docs.datadoghq.com/monitors/downtimes/?tab=bymonitorname#disable-first-recovery-notification), which is available in the Datadog API.I think it would be interesting to add it to complete the functional coverage of the Ansible module
Issue Type
Feature Idea
Component Name
datadog_downtime
Additional Information
Code of Conduct
The text was updated successfully, but these errors were encountered: