-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Viewer certificate conflict with cloudfront default certificate #7807
Labels
service/cloudfront
Issues and PRs that pertain to the cloudfront service.
Comments
ghost
mentioned this issue
Mar 4, 2019
bflad
added
the
service/cloudfront
Issues and PRs that pertain to the cloudfront service.
label
Mar 4, 2019
The fix for this (#7794) has just recently been merged and will release with version 2.1.0 of the Terraform AWS Provider, likely middle of this week. 👍 |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
ghost
locked and limited conversation to collaborators
Mar 31, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue was originally opened by @jackhardy1 as hashicorp/terraform#20556. It was migrated here as a result of the provider split. The original body of the issue is below.
I have recently been getting a certificate conflict error, and am now unable to perform any
terraform apply / terraform plan
actions. The error I have been getting is as follows:Error: module.<moduleName>aws_cloudfront_distribution.backoffice-api-cdn: 'viewer_certificate.0.acm_certificate_arn': conflicts with viewer_certificate.0.cloudfront_default_certificate
Error: module.<moduleName>.aws_cloudfront_distribution.backoffice-api-cdn: 'viewer_certificate.0.cloudfront_default_certificate': conflicts with viewer_certificate.0.acm_certificate_arn
Some of my colleagues, however, aren't experiencing this issue, and I don't think this is an issue with the state in S3. This may appear vague, but I'm afraid I'm not sure what the real issue of this problem is - any ideas on how to look into this would be greatly appreciated!
Terraform Version
0.11.11
The text was updated successfully, but these errors were encountered: