-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
Fix for #33 #70
Fix for #33 #70
Conversation
also mentioned at terraform-aws-modules#26 (comment)
also mentioned at terraform-aws-modules#26 (comment)
Hi @antonbabenko, |
I will try to take a look at this during this week. The solution is probably a bit more complicated than the fix you are proposing here so I can't just merge this easily with certaincy. |
Hello @antonbabenko, (it eliminates the edge case when "aws_acm_certificate" was not created or is not present in state, |
Unfortunately, I have not had time for this yet. |
@mslipets gently poking @antonbabenko just to remind. (if you don't mind =) |
@antonbabenko i'm afraid that #71 does not really closes #70, |
Ok. Please provide the exact values you are trying to pass to the module to get such an issue. I can see a lot of comments but nowhere I can see the actual code which does not work. It is just impossible for me to figure out the broken condition which the PR should fix. module "acm" {
source = "terraform-aws-modules/acm/aws"
domain_name = "my-domain.com"
zone_id = "Z2ES7B9AZ6SHAE"
# ??? what to put here to get the error ???
} |
I've also stumbled on this issue. I have 2 existing certificates in terraform. module "acm-mydomain" {
source = "terraform-aws-modules/acm/aws"
version = "3.0.0"
domain_name = "mydomain.com"
subject_alternative_names = ["*.mydomain.com"]
certificate_transparency_logging_preference = true
validate_certificate = false
}
module "acm-mydomain2" {
source = "terraform-aws-modules/acm/aws"
version = "3.0.0"
domain_name = "mydomain2.com"
certificate_transparency_logging_preference = true
validate_certificate = false
} I created a new certificate via the UI, now I wanted to import the existing certificate by creating the resource and running the import statement
Which throws an error for the existing certificates?
|
I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
in Motivation and Context ⤵
Motivation and Context
attempt to fix #33
also mentioned at #26 (comment)
Breaking Changes
No breaking changes.
How Has This Been Tested?
Tested on sandbox environment as a part of destroy phase,
otherwise destroy comes out with: