Skip to content
This repository has been archived by the owner on Dec 16, 2024. It is now read-only.

Pass hostPort explicitly in container definitions #464

Merged
merged 2 commits into from
Apr 25, 2018

Conversation

lukehoban
Copy link
Contributor

@lukehoban lukehoban requested review from pgavlin and mmdriley April 24, 2018 23:32
aws/service.ts Outdated
// However, if left blank, it will be automatically populated by AWS, potentially leading to dirty
// diffs even when no changes have been made. So we populate it with the same value as `containerPort`.
// See https://github.com/terraform-providers/terraform-provider-aws/issues/3401.
hostPort: p.targetPort || p.port,
Copy link
Member

Choose a reason for hiding this comment

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

Should we add a note about only doing this for networkMode: "awsvpc"?

Copy link
Member

Choose a reason for hiding this comment

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

(I see that the doc snippet you pulled mentions it, but it's easy to miss)

Copy link
Contributor

@mmdriley mmdriley left a comment

Choose a reason for hiding this comment

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

It might be worth leaving a comment at line 478 that, if we ever use something other than awsvpc, we'll need to revisit hostPort.

@lukehoban lukehoban force-pushed the lukehoban/hostport branch from a51fa95 to dbb960c Compare April 24, 2018 23:41
We've been seeing test flakiness when launching many tasks concurrently, likely related to #456.

For now, simplify the test.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants