Open 0x46616c6b opened 3 years ago
Seems that the team never read from the update request.
Hey Opsgenie team, is this going to be fixed soon?
The API behind this request doesn't accept team at this point-->
The API behind this request doesn't accept team at this point-->
This still appears to be true.
Example workaround (which can be simpler if your team id comes from a resource):
resource "terraform_data" "opsgenie-team-id" {
input = var.opsgenie_team_id
}
resource "opsgenie_service" "service" {
name = var.name
description = var.description
team_id = terraform_data.opsgenie-team-id.output
# Services do not appear to register changes to team IDs.
# See https://github.com/opsgenie/terraform-provider-opsgenie/issues/216,
# others.
lifecycle {
replace_triggered_by = [
terraform_data.opsgenie-team-id
]
}
}
Hello,
we run the latest version of the provider (
v0.5.7
) and try to adjust the resourceopsgenie_service
and want to change theteam_id
. In every plan and run the output brings changes to the resources but after successful run the origin is not adjusted.Terraform Version
0.14.3
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
When I change the
team_id
property I expected that the team will changed.Actual Behavior
The old team is not replaced with the new one.
Steps to Reproduce
Apply this config (two teams and one service)
Apply with changed
team_id
You will see that still Team One is connected with the service.