Open blabu23 opened 1 month ago
BTW: exactly the next 'terraform init -upgrade' a new provider version was released (v6.4.0). Too bad, it has the same bug ;-)
Thank you for reporting the issue. We have raised an internal ticket to track this. Our service engineers will get back to you.
Hi there! Any news? Are you able (and willing) to give me the ticket or SR so I can follow (and eventually deliver more information) it?
Hi @blabu23 , Thank you for reporting this bug. We have identified the issue and are working on the fix. But the testing and release process is long. The ETA of releasing the fix will be Sep 5th.
Community Note
Terraform Version and Provider Version
Terraform v1.9.2 on darwin_arm64
Affected Resource(s)
oci_containerengine_node_pool
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Since the line
fault_domains = [tolist(local.ad_fd_map[adi.value])]
(which results to this array: ["FAULT-DOMAIN-1", "FAULT-DOMAIN-2", "FAULT-DOMAIN-3"])
was newly added to the existing dynamic placement_configs block (it was not set before), I would expect a modification of my two nodepools in the OCI.
Actual Behavior
terraform plan does not detect this change and displays `No changes. Your infrastructure matches the configuration.'
Steps to Reproduce
terraform plan/apply
Important Factoids
When id add another option to the placement_configs block, e.g.
capacity_reservation_id = "bla"
, terraform finds also the changes to the fault_domains options and plans/applies them!References