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
There we can see that it's not passing the 'OwnerTeam' argument to the request. And in my trial runs using curl, I found that if I try to update an integration without passing the 'ownerTeam' argument in the JSON payload, it will result in the same error.
{"code":40301,"message":"You can not assign integration to another team","took":0.002,"requestId":"2986a890-3fd3-4f5e-973b-4e6034c5936a"}
Please note I am using an API key from an API integration which I have created under my 'team' to authenticate the SDK to OpsGenie. Could that be an issue?
The text was updated successfully, but these errors were encountered:
Hi,
I am getting the following error while trying to update an integration.
{"code":40301,"message":"You can not assign integration to another team","took":0.002,"requestId":"2986a890-3fd3-4f5e-973b-4e6034c5936a"}
I think this could be due to a bug in the function 'ForceUpdateAllFields'
https://github.com/opsgenie/opsgenie-go-sdk-v2/blob/v1.1/integration/integration.go#L57
There we can see that it's not passing the 'OwnerTeam' argument to the request. And in my trial runs using curl, I found that if I try to update an integration without passing the 'ownerTeam' argument in the JSON payload, it will result in the same error.
curl -X PUT 'https://api.eu.opsgenie.com/v2/integrations/<integration_id>' --header 'Authorization: GenieKey<API_KEY>' --header 'Content-Type: application/json' --data '{ "enabled": true, "ignoreRespondersFromPayload": true, "name": "<INTEGRATION_NAME>", "suppressNotifications": true, "responders": [], "type": "API" }'
{"code":40301,"message":"You can not assign integration to another team","took":0.002,"requestId":"2986a890-3fd3-4f5e-973b-4e6034c5936a"}
Please note I am using an API key from an API integration which I have created under my 'team' to authenticate the SDK to OpsGenie. Could that be an issue?
The text was updated successfully, but these errors were encountered: