Skip to content
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

Re-merge "Update aws-sdk gem version" #14817

Merged
merged 3 commits into from May 9, 2017
Merged

Re-merge "Update aws-sdk gem version" #14817

merged 3 commits into from May 9, 2017

Conversation

joshlory
Copy link
Contributor

@joshlory joshlory commented May 3, 2017

Re-merge PR #14798.

@joshlory joshlory changed the title Re-merge "Update aws-sdk gem version" #14814 Re-merge "Update aws-sdk gem version" May 3, 2017
custom_origin_config: {
origin_read_timeout: 5,
origin_keepalive_timeout: 30
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these lines need to be removed - only one of s3_origin_config or custom_origin_config are required.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do I add these options to s3_origin_config or remove them entirely?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove entirely.

@joshlory
Copy link
Contributor Author

joshlory commented May 3, 2017

Updated! Is there any way to test these changes before the merge to staging?

Copy link
Contributor

@wjordan wjordan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. For testing, test_cloudfront.rb ensures that the client is passing valid structures to the AWS API, but the AWS API itself performs extra validation that we can't test without a complete integration test. I've actually written such a test (see cookbooks/cdo-varnish/test/cookbooks/varnish_test), but since updating a CloudFront distribution can take up to an hour, it's currently just a manual test, so not feasible to add it to our continuous integration. So just merging to staging is fine

@ashercodeorg
Copy link
Contributor

@joshlory, our pipeline is pretty clean right now (about to get my third green DTT), if you want to merge this, I'm happy to deal with any fallout as DOTD.

@joshlory joshlory merged commit cb96204 into staging May 9, 2017
@joshlory joshlory deleted the update-aws-sdk-gem branch May 9, 2017 03:36
@joshlory
Copy link
Contributor Author

joshlory commented May 9, 2017

The Update CloudFront build step initially failed on merge. Succeeded after adding one more config option in 5abcb02.

https://codedotorg.slack.com/archives/C03CK8E51/p1494301821954043

}
},
origin_read_timeout: 5,
origin_keepalive_timeout: 30
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@joshlory turns out these values are mismatched, they should have been origin_read_timeout: 30, origin_keepalive_timeout: 5 to match the defaults. sorry for not picking this up earlier

joshlory added a commit that referenced this pull request May 10, 2017
@joshlory
Copy link
Contributor Author

Also needed one more config option: eeaa8af.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants