-
-
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
Make S3 website private; add S3 origin #105
Conversation
As I reported in #107, when using an S3 website origin, redirection from I am tempted to go further and make |
This pull request is now in conflict. Could you fix it @jmcgeheeiv? 🙏 |
@jmcgeheeiv can you fix the merge conflicts ? Also, it looks like PR #108 put in the following terraform-aws-cloudfront-s3-cdn/main.tf Lines 249 to 255 in 0818b34
How would that work with this PR ? does that PR make this one no longer relevant ? |
/test all |
This pull request is now in conflict. Could you fix it @jmcgeheeiv? 🙏 |
Okay @nitrocode, the code is tested with Terraform 0.13 and 0.14. The changes are in a single commit. I hope you can get this through before too many more commits come through. |
/test all |
It's not up to me. I'm not one of the approvers or in the engineering group. You'll have to be vocal in #pr-reviews channel to get this pr merged |
Please fix the tests. You need to add the random provider with a version pin |
This pull request is now in conflict. Could you fix it @jmcgeheeiv? 🙏 |
There are also a lot of prs going in and a recent bug i introduced. Let's get all the other stuff merged and come back to this one and then fix the conflicts. Otherwise you'll be driving yourself up a wall like me after every merge |
Okay, holding until I hear from you, @nitrocode. |
The bug was fixed in a now closed PR. Feel free to correct tests and fix conflicts. After you do, I'd post in #pr-reviews in slack to get attention to it. |
/test all |
@jmcgeheeiv looks like this one is close, but two things outstanding:
Get those updated and we'll give this a final pass and move it forward 🤙 |
* Add variable to specify S3 origins * URL subdir/ forwards to subdir/index.html (no Lambda function required!) * S3 website origin made private: CloudFront sends "referer" custom header to S3 website S3 website demands referer custom header * Merge my custom_headers with that added in #108 * In docs, warn the user to specify aliases with website_enabled * Change http_port and https_port from null to numbers. null causes a very, very hard-to-diagnose error
* Provide better description for var.origin_bucket * Auto Format * Update based on comments * Auto Format * Add example of reusing an s3 bucket * Auto Format * Correct naming order * Auto Format * Auto Format Co-authored-by: cloudpossebot <[email protected]>
@jmcgeheeiv something got gunked up with your PR / commits, so now we're seeing a changeset from a number of recent PRs instead of just your changes. Sorry for this but can you do something along the following lines to get things back in order?
Feel free to go about that differently if your git-fu is better than mine (not hard obviously). |
I force-pushed a better version. @Gowiem I think I see the error I made. Last time, I did something similar to the six step procedure you describe. However, the local working git checkout master
git pull --force origin master While I am certain there is a more elegant way to do this, this is what worked. |
/test all |
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 👍
@jmcgeheeiv these bats tests are still failing -- Mind looking into them?
|
/test all |
* Add support for query_string_cache_keys Fixes #156 Co-authored-by: cloudpossebot <[email protected]>
/test all |
1 similar comment
/test all |
@Gowiem, it seems that chatops |
@jmcgeheeiv that's correct 😄 Leads to some confusion, but I believe it's done because Cloud Posse is spending money on an AWS bill out of its own pocket each time tests are run so they like to guard the fact that it could potentially be abused and they'd end up paying the full bill. |
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.
I believe this looks good, but I want to get a second set of eyes on it as well before we call it merged since it's a bigger PR. @nitrocode you mind giving a second approval?
Quick, before cloudpossebot changes its mind! |
@Gowiem, yes, I was thinking that since |
the code changes lgtm but i've not super familiar with the implications of the changes, so i'd prefer to punt the actual merge to someone else. |
@woz5999 haha I'm in the same boat and wanted another contributor to help me share the merge burden due to the large set of changes, but I shouldn't try to put that on others. I'll merge and deal with the fallout if this blows up this popular module. @jmcgeheeiv I'll be pinging you if that happens 😉 |
Thanks for the contribution @jmcgeheeiv (and working through our fun hoops on this one in particular)! Released as 0.61.0! |
What
In this PR I added these enhancements:
http_port
andhttps_port
to numbers merely to dissuade observers from attempting to usenull
.null
causes a very, very hard-to-diagnose error that does not reveal the line number.I will further note that Terraform insists that the complete data structure appearing in
variables.tf
be specified forcustom_origin
ands3_origin
variables. Thuslookup()
with default values is immaterial.Why
The reasons are included in the list of enhancements above. I hope it is more readable that way.