When the values are Computed: true terraform ends up using false for boolean values and 0 for integer values. In some cases this is not the true default value when creating a saved search, so this produces behavior that's inconsistent with creating a new alert through the Splunk UI.
Changing these defaults here to match Splunk's defaults for saved searches.
This change also removes some omitempty tags for integer values when transforming the struct to url parameters. Go's behavior is to consider 0 as an empty value so if the integer was set to 0 the field was not being included in the POST request to Splunk. This made it impossible to set one of these values to 0.
This issue is similar to #35, but concerns integer values.
Description
When the values are
Computed: true
terraform ends up usingfalse
for boolean values and0
for integer values. In some cases this is not the true default value when creating a saved search, so this produces behavior that's inconsistent with creating a new alert through the Splunk UI.Changing these defaults here to match Splunk's defaults for saved searches.
This change also removes some
omitempty
tags for integer values when transforming the struct tourl
parameters. Go's behavior is to consider0
as an empty value so if the integer was set to0
the field was not being included in the POST request to Splunk. This made it impossible to set one of these values to0
.This issue is similar to #35, but concerns integer values.