Using the Opsgenie Terraform provider with JSM

[Lewis Vail]

My team is migrating from a stand-along Opsgenie instance to the Opsgenie solution offered within JSM. Prior to moving we used terraform to define our integrations, on-call rotations, escalation policies, etc. but I'm unable to get this to work with our JSM instance. I created an "API" integration within the JSM Operations module just as we did with our standalone Opsgenie instance but when I try to run terraform I get the following error message:

Error occurred with Status code: 403, Message: Account is consolidated.

Is this functionality not supported by the JSM version or am I missing something? One difference I did notice with the API integration setup is that I wasn't allowed to enable the following permissions (which were available in my stand-alone Opsgenie instance):

• Allow Read Access
• Allow Create and Update Access
• Allow Delete Access
• Allow Configuration Access

[Deeksha]

Hi @Lewis Vail , 

This is Deeksha from the product management team, I just wanted to share the relevant document to ensure the right configurations steps and resources were being used - https://support.atlassian.com/jira-service-management-cloud/docs/set-up-atlassian-operations-terraform-provider/ 

There is a new Atlassian operations terraform provider that needs to be used for JSM operations configurations as we leverage the new JSM Operations API endpoints for the same.