-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Component/s: Operations - Integrations, Operations - Terraform Provider
-
1
-
Severity 1 - Critical
Issue Summary
In the UI, the teams are added to the Integration > Incoming Rules > Responder field. However, after a Terraform build failed attempt the teams stop being added as responders to the alerts, even with the responder field having the Team added to the UI.
Please review the persistence model while applying changes with Terraform to ensure that the previous values are used if a failure occurs.
Steps to Reproduce
Step 1
In an environment with JSM Operations Integrated with Pingdom, for example, leave the Assignee team option as None (Global integration) and add a responder team to one of the Incoming rules.
Step 2
Add an Incoming rule to Create Alert and add a Responder team to the respective field. For example
![]()
Step 3
Using Terraform Integration action resource attempt to rebuild the incoming rule.
Step 4
Create an Alert from Pingdom to create an Alert in JSM Operations.
Expected Results
The Alert is created in JSM Operations meeting the integration incoming rules conditions, and the Responder team is added to the JSM Alert after a failed Terraform build attempt.
Actual Results
The Alert is created in JSM Operations meeting the integration incoming rules conditions, and the Responder team is NOT added to the JSM Alert after a failed Terraform build attempt.
Workaround
Edit the integration > Incoming rule and remove the responder team. Save.
Edit the integration > Incoming rule and add the responder team again. Save.