You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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. 👍
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: