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
During the migration to the new runtime (PR 1 adding the new runtime, PR 2 removing the old runtime), the
DEVELOP
live debugging functionality was missed. This workflow, coupled with usinglocalstack.dev.run
is crucial for debugging parts of LocalStack that only work when run from a container, e.g. testing inter-container Docker networking via services.Changes
DEVELOP
functionality back, including launching thedebugpy
debuggerDEVELOP=1
WAIT_FOR_DEBUGGER=1
debugpy
withDEVELOP_PORT
(default: 5678)localstack.dev.run
where community only entrypoints were not being mounted from the correct place (when launched from a community checkout)localstack.dev.run
where community and pro entrypoints were not being mounted from the correct place (when launched from a pro checkout)HostPaths
to access source code checkout paths on the hostTesting
master
localstack.dev.run --mount-entrypoints
localstack.dev.run --mount-entrypoints
localstack.dev.run --mount-entrypoints --develop
debugpy
is being installed, and is available on port 5678