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
When setting edge_ips_connectivity to "ipv4" in an ibm_cis_range_app resource, Terraform always detects it as "all" in the state and tries to change it back to "ipv4" during every plan/apply cycle.
The change never actually takes effect, resulting in a constant drift between desired and actual state.
Expected Behavior
Once edge_ips_connectivity is set to "ipv4", it should persist in that state
Problem
This appears to be a provider-side issue where the value is either not being correctly sent to the API or not being correctly read from the API response.
Description
When setting
edge_ips_connectivity
to "ipv4" in anibm_cis_range_app
resource, Terraform always detects it as "all" in the state and tries to change it back to "ipv4" during every plan/apply cycle.The change never actually takes effect, resulting in a constant drift between desired and actual state.
Expected Behavior
Once edge_ips_connectivity is set to "ipv4", it should persist in that state
Problem
This appears to be a provider-side issue where the value is either not being correctly sent to the API or not being correctly read from the API response.
Maybe this is the case because checking twice: cisRangeAppEdgeIPsType ==> https://github.com/IBM-Cloud/terraform-provider-ibm/blob/master/ibm/service/cis/resource_ibm_cis_range_app.go#L371-L374
The text was updated successfully, but these errors were encountered: