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

Release: 0.6.2 Release #752

Merged
merged 25 commits into from
Nov 7, 2018
Merged

Release: 0.6.2 Release #752

merged 25 commits into from
Nov 7, 2018

Conversation

sriram-mv
Copy link
Contributor

jfuss and others added 25 commits October 18, 2018 08:35
Address #669

Docker only supports attaching containers to the host network through
the network_mode in the create. Previously, we tried to attach the
container to the host network after creating. This caused the command
to fail. Docker does not support attaching a container to host and bridge.
Therefore, we need to handle host as a special case.
chore: Enable Travis to run integ tests
* fix: upgrade requests to 2.20.0

Addresses vulnerability: https://nvd.nist.gov/vuln/detail/CVE-2018-18074

* fix: change assertion in api gateway func tests
Travis expects output from commands and if no ouput is recieved,
Travis kills the build thinking command has stalled. Some of our
integ tests cause this issue in travis: https://travis-ci.org/awslabs/aws-sam-cli/jobs/447830765

This commit adds travis_wait to our integ test command. Details on
this can be found here: https://docs.travis-ci.com/user/common-build-problems/#my-builds-are-timing-out
fix: Support attaching to host network
chore(version_bump): bump to 0.6.2
@sriram-mv sriram-mv merged commit 5febb4e into master Nov 7, 2018
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

8 participants