Inconsistent final plan when using custom_origin in Cloudfront #11235
Labels
service/cloudfront
Issues and PRs that pertain to the cloudfront service.
service/elasticbeanstalk
Issues and PRs that pertain to the elasticbeanstalk service.
service/elb
Issues and PRs that pertain to the elb service.
service/iam
Issues and PRs that pertain to the iam service.
service/s3
Issues and PRs that pertain to the s3 service.
waiting-response
Maintainers are waiting on response from community or contributor.
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/gnouts/1a7581816e3c79a2d6779c28c733d268
Panic Output
Expected Behavior
CloudFront should have been updated correctly.
Actual Behavior
Terraform crashes and does not complete other action.
Steps to Reproduce
terraform init
terraform apply
-> this one should be ok.terraform apply
-> Second run crashes !Important Factoids
In my VPC, I create a public subnet that contains the Beanstalk's ELB and a private subnet that contains the Beanstalk's EC2.
I'm using CloudFront to serve my static front from S3 and redirect API calls to Beanstalk's ELB.
If you comment the second origin (custom origin redirecting to beanstalk) in cloudfront everything work fine.
References
I have reported another issue, which this one is an extension using the same code base, so might be related.
#11217
The text was updated successfully, but these errors were encountered: