Modification of non existing fields #161
Comments
cwjohnston
added a commit
to cwjohnston/terraform-provider-splunk
that referenced
this issue
Dec 12, 2024
As mentioned in splunk#161, terraform plan shows changes to saved search parameters action_jira_service_desk_param_jira_description and action_jira_service_desk_param_jira_summary when using the defaults for those parameters. From what I can tell, the default values are computed server-side by Splunk. I believe this change will suppress superfluous changes to these Jira parameters, but may break in the future if the Splunk -computed defaults were to change.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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_jira_descritpion" 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?
Regards
The text was updated successfully, but these errors were encountered: