-
-
Notifications
You must be signed in to change notification settings - Fork 248
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
Feat: Add external_aliases
Which Will Not Have CNAMEs Created for Them
#199
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change details
-
Error ID Change Path Resource BC_AWS_GENERAL_27 Added /main.tf aws_cloudfront_distribution.default BC_AWS_GENERAL_56 Added /main.tf aws_s3_bucket.origin BC_AWS_NETWORKING_52 Added /main.tf aws_s3_bucket.origin BC_AWS_GENERAL_72 Added /main.tf aws_s3_bucket.origin
@mburns are you able to please add BridgeCrew exceptions for the failing checks outlined in this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. But please see comments regarding BridgeCrew.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change details
-
Error ID Change Path Resource BC_AWS_GENERAL_27 Fixed /main.tf aws_cloudfront_distribution.default BC_AWS_GENERAL_56 Fixed /main.tf aws_s3_bucket.origin BC_AWS_NETWORKING_52 Fixed /main.tf aws_s3_bucket.origin BC_AWS_GENERAL_72 Fixed /main.tf aws_s3_bucket.origin
This Pull Request has been updated, so we're dismissing all reviews.
This reverts commit fac591c.
Hey @mburns — I see that you reverted the BridgeCrew supressions, was there a particular reason why? |
HI @korenyoni, just troubleshooting, sorry. It looked like the errors were fixed just by merging the latest master. I'll re-apply the change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change details
-
Error ID Change Path Resource BC_AWS_GENERAL_27 Fixed /main.tf aws_cloudfront_distribution.default BC_AWS_NETWORKING_52 Fixed /main.tf aws_s3_bucket.origin BC_AWS_GENERAL_56 Fixed /main.tf aws_s3_bucket.origin BC_AWS_GENERAL_72 Fixed /main.tf aws_s3_bucket.origin
/test all |
@mburns I'm honestly not sure why the BridgeCrew check is still failing — I will have to take a closer look tomorrow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change details
-
Error ID Change Path Resource BC_AWS_NETWORKING_52 Fixed /main.tf aws_s3_bucket.origin BC_AWS_GENERAL_56 Fixed /main.tf aws_s3_bucket.origin BC_AWS_GENERAL_27 Fixed /main.tf aws_cloudfront_distribution.default BC_AWS_GENERAL_72 Fixed /main.tf aws_s3_bucket.origin
…3 bucket resource definition.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change details
-
Error ID Change Path Resource BC_AWS_GENERAL_27 Fixed /main.tf aws_cloudfront_distribution.default BC_AWS_NETWORKING_52 Fixed /main.tf aws_s3_bucket.origin BC_AWS_GENERAL_56 Fixed /main.tf aws_s3_bucket.origin BC_AWS_GENERAL_72 Fixed /main.tf aws_s3_bucket.origin
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change details
-
Error ID Change Path Resource BC_AWS_GENERAL_56 Fixed /main.tf aws_s3_bucket.origin BC_AWS_GENERAL_72 Fixed /main.tf aws_s3_bucket.origin BC_AWS_NETWORKING_52 Fixed /main.tf aws_s3_bucket.origin BC_AWS_GENERAL_27 Fixed /main.tf aws_cloudfront_distribution.default
/test all |
I'm still not sure why BC is failing in the GitHub checks API. Originally, it was because I'm not sure why it's still happening though. As you can see, it's passing in BC itself. @mburns I've also taken over your PR and just expanded the suppression comments and moved the suppressions to the top of the resource definition blocks. Anyways, I'm going to merge this in and hope the BC errors do not keep happening in subsequent PRs. |
external_aliases
Which Will Not Have CNAMEs Created for Them
what
why
dns_alias_enabled
, but allows for a mixture of DNS providers for a single CloudFront Distribution