Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ibm_cis_range_app | IPv4 edge_ips_connectivity setting not persisting in ibm_cis_range_app #5924

Open
MaAd12345 opened this issue Jan 17, 2025 · 0 comments
Labels
service/Internet Services Issues related to Cloud Internet Service (CIS)

Comments

@MaAd12345
Copy link

Description

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.

  ~ resource "ibm_cis_range_app" "range_app_default" {
      ~ edge_ips_connectivity = "all" -> "ipv4"

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

@github-actions github-actions bot added the service/Internet Services Issues related to Cloud Internet Service (CIS) label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service/Internet Services Issues related to Cloud Internet Service (CIS)
Projects
None yet
Development

No branches or pull requests

1 participant