add container port and volume flags to localstack start #9109
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We want to make it easier to add customizations when running
localstack start
. For instance, to generalize something likeDNS_ADDRESS
, we could just provide a port mapping forlocalstack start
, that allows people to map, say,127.0.0.1:1053:53/udp
. Similarly, there's now easy way to mount custom volumes into the localstack container other than usingDOCKER_FLAGS
.This PR adds a
-p
and-v
flag tolocalstack start
, which are the same as the flags used indocker run
. This is a continuation of #8772Changes
-p/--publish
and-v/--volume
flags tolocalstack start
ContainerConfigurators
:ro
suffix was provided/<protocol>
suffix or port range<start>-<end>
to be parsed correctly