You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I would like to be able to define a PagerDuty service, StatusCake integration, contact group, and test as a single set of entities within Terraform. This would allow for generating reporting groups for websites from existing service metadata.
Currently this is mostly achievable, except for one manual step of creating the PagerDuty integration with StatusCake, taking the resulting ID and adding it to a terraformed statuscake_contact_group.
Describe the solution you'd like
Adding a resource that allows the creation of integrations.
With the exception of phonecall and slack, the integrations have minimal config; for the scope of what I'm looking for, these could just be excluded from the capabilites.
Additional context
Taking a look at the StatusCake API documentation, the underlying problem may be that these are not an exposed API?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I would like to be able to define a PagerDuty service, StatusCake integration, contact group, and test as a single set of entities within Terraform. This would allow for generating reporting groups for websites from existing service metadata.
Currently this is mostly achievable, except for one manual step of creating the PagerDuty integration with StatusCake, taking the resulting ID and adding it to a terraformed
statuscake_contact_group
.Describe the solution you'd like
Adding a resource that allows the creation of integrations.
With the exception of phonecall and slack, the integrations have minimal config; for the scope of what I'm looking for, these could just be excluded from the capabilites.
Additional context
Taking a look at the StatusCake API documentation, the underlying problem may be that these are not an exposed API?
The text was updated successfully, but these errors were encountered: