You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have found a bug when using splunk_authorization_roles, the 0 won't take effect for search_jobs_quota,search_time_winsearch_disk_quota , realtime_search_jobs_quota , it will just use the default values instead 0 if we specify 0 for these fields, but I verified API accept 0 values. And a bigger issue is if I update these fields with 0 to replace old values, the terraform plan will show these as changes and if we apply, it will show applied successfully, but they are actually not been applied and still using the previous values, please check the screenshots that after we do plan and apply
and this is the screenshot of statefile after apply and you can see these values are not updated to 0.
The text was updated successfully, but these errors were encountered:
hsy3418
changed the title
[Bug] realtime_search_jobs_quota 0 isn't taken as valid value for some fields.
[Bug] splunk_authorization_roles 0 isn't taken as valid value for some number fields.
May 3, 2021
I have found a bug when using splunk_authorization_roles, the 0 won't take effect for
search_jobs_quota
,search_time_win
search_disk_quota
,realtime_search_jobs_quota
, it will just use the default values instead 0 if we specify 0 for these fields, but I verified API accept 0 values. And a bigger issue is if I update these fields with 0 to replace old values, the terraform plan will show these as changes and if we apply, it will show applied successfully, but they are actually not been applied and still using the previous values, please check the screenshots that after we do plan and applyand this is the screenshot of statefile after apply and you can see these values are not updated to 0.
The text was updated successfully, but these errors were encountered: