Open jamiejackson opened 2 months ago
(#246 might be another example of an inappropriate circular relationship.)
We wanted to start using terraform for setup and we got the same issue with webhook integration. Hopefully someone work on this bug. We use version 1.0.90
I could temporary bypass it, hopefully
resource "site24x7_webhook_integration" "webhook_integration" {
...
monitors = []
lifecycle {
ignore_changes = [monitors]
}
}
Provider version 1.0.84 forces both sides of the Integration/Monitor† relationship to be defined, which is inappropriate. Other providers do this via association resources or they allow the relationship to be set on one side of the relationship.
†There may be other circular resource dependencies in the provider that need to be worked out, as well, but I'm starting with this one.
I'd suggest studying how some of the big providers do many-to-many relationships and pick/implement an option that makes sense.
There are problems with the current behavior. Here are two of them:
terraform plan
.At first blush, I think it probably makes the most sense to define the integration relationship from the monitor side, which would look like this:
Here is the fuller example of my current, problematic use case, as I am forced to implement it now.