Closed cbaxtersf closed 1 year ago
Figured out that this is related to permission issue and schedule_priority
. Once either removing schedule_priority
or setting right permissions it worked. Related to https://github.com/splunk/terraform-provider-splunk/pull/153
I have a project that contains numerous
splunk_saved_searches
. On the initial creation/apply of the resources everything creates just fine. When I go to update one of the resources, Terraform locally shows that there are changes via a plan. Terraform cloud then shows the same changes and applies them fine. After the apply, looking at the resources, I can see that the apply did not actually happen. Then running a plan either locally or within Terraform Cloud, shows the same changes needing to be applied again. I can do plan/apply over and over in Terraform cloud and nothing changes in Splunk. In order to fix the issue, I have to delete the resources in Splunk and then remove the modules from the Terraform state file. After that, the next apply re-creates the resources correctly.Example resource:
What is changing between applies is the search or creating as an alert vs a report. In either case, the apply says it worked but it actually didn't change anything within Splunk.
This is running on provider version v1.4.9.