In v8.2, a string is returned for maxHotBuckets when terraform is making an api request against for indexes. The maxHotBuckets was an integer in previous version, which is what terraform-provider-splunk is expecting here
Rest api url: https://splunkserver.com/services/data/indexes?output_mode=json
If the key does exist in the schema but doesn't exist in the configuration, then the default value for that type will be returned. For strings, this is "", for numbers it is 0, etc
Applying the above plan has no affect on the max_hot_buckets.
One option for v8.2 is the change the data type to String here, here and here. Then the plan shows no changes
But the provider needs a solution to support both 8.2 and previous versions.
Update
Looks like this is being addressed in this PR
In v8.2, a string is returned for
maxHotBuckets
when terraform is making an api request against for indexes. ThemaxHotBuckets
was an integer in previous version, which is whatterraform-provider-splunk
is expecting hereRest api url:
https://splunkserver.com/services/data/indexes?output_mode=json
Splunk documents this change in the index.conf 8.0.3 indexes.conf doc:
8.2.6 indexes.conf doc:
The result is that terraform is trying to update the maxHotBuckets every time a plan is created, so in my case,
ResourceData.Get why the provider returns a 0.
Applying the above plan has no affect on the
max_hot_buckets
.One option for v8.2 is the change the data type to String here, here and here. Then the plan shows no changes
But the provider needs a solution to support both 8.2 and previous versions.
Update Looks like this is being addressed in this PR