-
Notifications
You must be signed in to change notification settings - Fork 48
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
Add data sources for sysdig monitor notification channels #138
Comments
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Please keep open, we would still like this feature. |
* Add data sources for PagerDuty and email notification channels Part of: #138 * ci: Add extra verification checks * docs: Add documentation for missing data sources * fix(docs): Add line break Co-authored-by: Ryan Moe <ryan.moe@ibm.com> Co-authored-by: Fede Barcelona <fede_rico_94@hotmail.com>
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Released with v0.5.30. (pagerduty and email at least which is what we needed, feel free to keep adding more for slack and others) |
It would be really helpful if we could have data sources for sysdig monitoring notification channels. In some of our environments we end up creating and maintaining sysdig monitor instances and their notification channels in one module and alerts get created in several other modules depending on the environment/application/etc.
The current work around is to maintain outputs from one module and use remote data sources elsewhere which is cumbersome, prone to errors and I would not be surprised if Hashicorp stops supporting it down the line.
The text was updated successfully, but these errors were encountered: