I'm currently using the terraform splunk provider in order to create and manage alerts in Splunk cloud. I was until recently using v1.4.13 and had no problems with it. However i've had to upgrade to 1.4.18 in order to add Jira actions to those alerts.
Upon upgrading i now see the following whenever i start a terraform plan:
The issue is that the fields "action_jira_service_desk_param_jiradescritpion" and "action..._summary" have never been defined be it in Splunk or in the terraform file so i do not understand why terraform is suddenly trying to delete them.
I see these two actions for every alerts and reports i have created so far using terraform.
This in itself wouldn't be too much of a problem if the apply went through, however it doesn't as i get a context deadline exceeded error everytime i try to run it as shown in the picture below.
I have tried to look this issue up and have been unable to find a working solution.
Do you have any ideas why terraform detects "non-existing" fields and/or why the apply fails?
Hello,
I'm currently using the terraform splunk provider in order to create and manage alerts in Splunk cloud. I was until recently using v1.4.13 and had no problems with it. However i've had to upgrade to 1.4.18 in order to add Jira actions to those alerts. Upon upgrading i now see the following whenever i start a terraform plan:
The issue is that the fields "action_jira_service_desk_param_jiradescritpion" and "action..._summary" have never been defined be it in Splunk or in the terraform file so i do not understand why terraform is suddenly trying to delete them.
I see these two actions for every alerts and reports i have created so far using terraform.
This in itself wouldn't be too much of a problem if the apply went through, however it doesn't as i get a context deadline exceeded error everytime i try to run it as shown in the picture below.![image](https://github.com/splunk/terraform-provider-splunk/assets/46690384/520b77cf-2bc4-4752-9ea4-5fd1368806b4)
I have tried to look this issue up and have been unable to find a working solution. Do you have any ideas why terraform detects "non-existing" fields and/or why the apply fails?
Regards