Fix changing the owner team of an API integration (#146)

Fixes an issue where owner team ID could not be changed when linked with integration actions. The fix creates a new integration when the owner team is changed.
opsgenie · Jul 12, 2023 · 3f3374d · 3f3374d
1 parent fb911a6
commit 3f3374d
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 1 deletion.
diff --git a/opsgenie/resource_opsgenie_api_integration.go b/opsgenie/resource_opsgenie_api_integration.go
@@ -51,6 +51,7 @@ func resourceOpsgenieApiIntegration() *schema.Resource {
 			"owner_team_id": {
 				Type:     schema.TypeString,
 				Optional: true,
+				ForceNew: true,
 			},
 			"api_key": {
 				Type:      schema.TypeString,

diff --git a/website/docs/r/api_integration.html.markdown b/website/docs/r/api_integration.html.markdown
@@ -78,7 +78,7 @@ The following arguments are supported:
 
 * `suppress_notifications` - (Optional) If enabled, notifications that come from alerts will be suppressed. Default: `false`.
 
-* `owner_team_id` - (Optional) Owner team id of the integration.
+* `owner_team_id` - (Optional, Forces new resource) Owner team id of the integration. If changed, this will recreate a new API integration, which will probably have a different API key.
 
 * `responders` - (Optional)  User, schedule, teams or escalation names to calculate which users will receive the notifications of the alert.