Closed vburckhardt closed 5 months ago
is the problem related to these defined locals here: https://github.com/terraform-ibm-modules/terraform-ibm-key-protect/pull/534
cc @MatthewLemmond
Tested this locally using the non-modified output from the kms instance policy resource block and it has the same issue likely due to the same root problem with the outputs from the provider being improperly formatted thus terraform always thinks the output does not match its expected value. I don't think we would be able to resolve this drift without https://github.com/IBM-Cloud/terraform-provider-ibm/issues/5163 being resolved first.
I do have a couple more things to test on this to see if we can resolve the drift issue so will continue looking at this.
@MatthewLemmond - Is this issue fixed? Will made fix for https://github.com/IBM-Cloud/terraform-provider-ibm/issues/5163. Can you please validate?
@bhakta-ibm Yes, issue with idempotency/drift is resolved, we will create a PR for https://github.com/terraform-ibm-modules/terraform-ibm-key-protect to require 1.65.0 once it is out of beta and the consuming modules (such as this one) will then be updated to match.
PRs merged, closing
Detected by Project on daily scans.
Affected modules
*
Terraform CLI and Terraform provider versions
Terraform output
Debug output
Expected behavior
Actual behavior
Steps to reproduce (including links and screen captures)
terraform apply
Anything else
By submitting this issue, you agree to follow our Code of Conduct