scaleway_rdb_acl not statefull

[SebastienLQ]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v1.0.8
on linux_amd64

• provider registry.terraform.io/hashicorp/template v2.2.0
• provider registry.terraform.io/scaleway/scaleway v2.1.0

Affected Resource(s)

• scaleway_rdb_acl

Terraform Configuration Files

resource scaleway_rdb_acl main {
  instance_id = scaleway_rdb_instance.main.id
  acl_rules {
        description = "all"
        ip          = "0.0.0.0/0"
        }
  acl_rules {
        description = "kube1"
        ip          = "${scaleway_instance_ip.public_ip_c1.address}/32"
        }
  acl_rules {
        description = "kube2"
        ip          = "${scaleway_instance_ip.public_ip_c2.address}/32"
        }
  acl_rules {
        description = "kube3"
        ip          = "${scaleway_instance_ip.public_ip_c3.address}/32"
        }
  acl_rules {
        description = "ip_lb_infra"
        ip          = "${scaleway_lb_ip.ip.ip_address}/32"
        }
}

Debug Output

scaleway_rdb_acl issue

Expected Behavior

no change in terraform configuration file => no change in resource state

Actual Behavior

As we can see on the debug output, acl_rules changes each other A replace B which replace C wich replace A.
there is always a modification in the state of your scaleway_rdb_acl

Steps to Reproduce

just put more than 1 acl_rules in your scaleway_rdb_acl resource

1. terraform apply -auto-approve
2. terraform apply -auto-approve
3. ...

References

NONE