-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Description
Hello everyone! We have launched a major release of LocalStack! There are some significant changes coming up, and we would like to use this issue to keep you up to date.
Timeline
- Friday July 8., 2022: tagged release of v0.14.5, which will be the last release in v0
- Monday July 11., 2022:
⚠️ we will merge our release branch v1 into master, which will update thelatest
Docker image to contain the current version of v1, and will potentially affect your pipeline if you are usinglatest
. v1 release PR #6272 - Wednesday July 13., 2022: release will be created with a tag v1.0.0
What's changed?
You can find the final release notes here: https://github.com/localstack/localstack/releases/tag/v1.0.0
Here are the draft notes we prepared for this issue:
Community Features and Major Changes
- New filesystem hierarchy with simplified configuration
- Full rollout of the AWS Server Framework (ASF)
- A framework for testing and reporting parity with AWS
- All new logging output for and improved error reporting
- Remove deprecated persistence provider
Pro Features
- Cloud Pods experience
- Revamp of multi-account setups (experimental)
- Introducing Extensions (experimental)
- Access to detailed telemetry of your stacks
- IAM enforcement for all services
How to Migrate
- Update your startup configurations to the new LocalStack volume directory)
-
Starting with docker-compose:
Update your volumes mounts fromvolumes: - "${TMPDIR:-/tmp}/localstack:/tmp/localstack"
to
volumes: - "${LOCALSTACK_VOLUME_DIR:-./volume}:/var/lib/localstack"
-
Starting with docker directly:
Update your volume mounts from
docker run -p 4566:4566 -v /tmp/localstack:/tmp/localstack ...
to
docker run -p 4566:4566 -v /path/to/volume:/var/lib/localstack ...
where/path/to/volume
should be something outside your host’s temp folder. We encourage the cache directory of your system -
Starting with the CLI:
Just update to the latest version of the CLI withpip install --upgrade localstack
. The latest version of the CLI already uses the new LocalStack volume directory.
The volume directory can be configured via theLOCALSTACK_VOLUME_DIR
, which defaults to:- Mac:
~/Library/Caches/localstack/volume
- Linux:
~/.cache/localstack/volume
- Windows:
%LOCALAPPDATA%/localstack/cache/volume
- Mac:
-
- The old filesystem hierarchy (including
/tmp/localstack
mounts,DATA_DIR
andHOST_TMP_PATH
) can be enabled usingLEGACY_DIRECTORIES=1
- If you mount a volume into
/tmp/localstack
instead of/var/lib/localstack
, then LocalStack will automatically enableLEGACY_DIRECTORIES=1
, and print a deprecation warning. - You currently cannot set the configure the new filesystem hierarchy with the CLI version
0.14.x
, in order to use the development version of the cli, please runpip install --upgrade "localstack>=1.0.0.dev"
- Remove
DATA_DIR
which has been deprecated and will be ignored. UsePERSISTENCE=1
and find your state files in your LocalStack volume instate/
- Remove
HOST_TMP_PATH
, which was previously necessary forLAMBDA_EXECUTOR=docker
ordocker-reuse
. We now detect automatically the host path that is mounted into Lambda containers from your LocalStack volume mount. - When using docker-compose, remove the
network_mode: bridge
configuration unless you are sure that you need it. We now automatically detect the network mode for Lambda networking. - We’ve rolled out a completely new framework for handling AWS requests, the AWS Server Framework (ASF). This has replaced the edge proxy, which was previously handling all HTTP requests. If you are experiencing problems, as a workaround you can try to enable the old edge proxy with
LEGACY_EDGE_PROXY=1
but this is deprecated and will be removed in the future. - Enable the experimental multi-accounts feature by setting
MULTI_ACCOUNTS=1
as part of your LocalStack config. New AWS accounts will be allocated based on configuration from the client side. See docs for details. - Replay-based persistence as been removed. To use our more mature persistence mechanism, please consider upgrading to LocalStack Pro.