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

DXE-3283 Using akamai_appsec_ip_geo resource without explicitly setting ukraine_geo_control_action always produces a diff #484

Closed
stigok opened this issue Oct 18, 2023 · 4 comments

Comments

@stigok
Copy link

stigok commented Oct 18, 2023

Running plan for a akamai_appsec_ip_geo resource without explicitly setting ukraine_geo_control_action to "none" always produces a diff.

Terraform Version

Terraform v1.6.1
on linux_amd64
+ provider registry.terraform.io/akamai/akamai v5.3.0

Affected Resource(s)

  • akamai_appsec_ip_geo

Terraform Configuration Files

resource "akamai_appsec_ip_geo_protection" "web-services" {
  config_id          = akamai_appsec_configuration.web-services.config_id
  security_policy_id = akamai_appsec_security_policy.web-services.security_policy_id
  enabled            = true
}

Debug Output

N/A

Panic Output

N/A

Expected Behavior

No diff produced

Actual Behavior

  # akamai_appsec_ip_geo.web-services will be updated in-place
  ~ resource "akamai_appsec_ip_geo" "web-services" {
        id                         = "redacted"
      - ukraine_geo_control_action = "none" -> null
        # (6 unchanged attributes hidden)
    }

Steps to Reproduce

  1. terraform apply

Important Factoids

N/A

References

N/A

@PawelSnoch
Copy link

Hello @stigok
Thank you for opening the issue. We have some difficulties with recreating your bug. Your issue is about resource "akamai_appsec_ip_geo", but in terraform config you mentioned about resource "akamai_appsec_ip_geo_protection".
Could you please provide whole necessary config to reproduce your case?

Best regards,
Pawel

@wzagrajcz wzagrajcz changed the title Using akamai_appsec_ip_geo resource without explicitly setting ukraine_geo_control_action always produces a diff DXE-3283 Using akamai_appsec_ip_geo resource without explicitly setting ukraine_geo_control_action always produces a diff Oct 23, 2023
@BAu0002
Copy link

BAu0002 commented Jan 22, 2024

I too have the same issue with ukraine_geo_control_action.

Where the "resource "akamai_appsec_ip_geo" "ipGeo" {" resource does not declare ukraine_geo_control_action will result in a diff in terraform plan

Here's sample code:
resource "akamai_appsec_ip_geo" "ipGeo" {
config_id = var.configId
security_policy_id = akamai_appsec_ip_geo_protection.ipGeoProtection.security_policy_id
mode = block
geo_network_lists = var.geoNetworkLists
ip_network_lists = var.ipNetworkLists
exception_ip_network_lists = var.exceptionIpNetworkLists
}

Terraform plan code:
~ resource "akamai_appsec_ip_geo" "ipGeo" {
id = "1234:xxxx"
- ukraine_geo_control_action = "none" -> null
# (6 unchanged attributes hidden)
}

@PawelSnoch
Copy link

Hello @BAu0002 ,

thank you for your update and terraform code. I was able to reproduce this issue.
We will inform you about any progress.

Thanks,
Pawel

@lkowalsk-akamai-com
Copy link
Contributor

lkowalsk-akamai-com commented Mar 26, 2024

This issue should be fixed with recent release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants