Closed SimonEdwardsMQA closed 1 year ago
@SimonEdwardsMQA Please check if the mentioned criteria are met. https://github.com/hashicorp/terraform-provider-aws/issues/8925#issuecomment-500480461
@SimonEdwardsMQA Please check if the mentioned criteria are met. hashicorp/terraform-provider-aws#8925 (comment)
The issue isn't with the cert itself, that is eligible, the problem I'm having is setting the renewal_eligibility so that Terraform is aware that it's eligible.
As far as I understood renewal_eligibility
can not be managed directly by the AWS provider and is just provided as output.
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/acm_certificate#renewal_eligibility
How do I get around the "Objects have changed outside of Terraform" issue when I run a plan? There must be something in TF that is trying to set renewal_eligibility
I agree with @dhoppe and there is nothing we can do in this module. It is Terraform AWS provider issue.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Is your request related to a problem? Please describe.
Since creating the certificate with this module, the renewal_eligibility has been changed to "ELIGIBLE". However, the module wants to revert this back to "INELIGIBLE" and I can't see a way of setting this or where the module is setting this argument.
Describe the solution you'd like.
Allow renewal_eligibility = "ELIGIBLE" to be accepted by the module.
Describe alternatives you've considered.
I'm unable to use ignore_changes
Additional context