@localstack/lstk_darwin_amd64 0.15.0 → 0.16.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,440 @@
+# lstk
+
+**A command-line interface for LocalStack**. Built in Go with a modern terminal UI and native CLI experience for managing and interacting with LocalStack deployments. 👾
+
+
+```bash
+npm install -g @localstack/lstk
+```
+
+See [installation](#installation) below.
+
+## Prerequisites
+
+- [Docker](https://docs.docker.com/get-docker/) — required as a container engine.
+- [LocalStack account](https://app.localstack.cloud) — required for credentials, the CLI will guide you through authentication.
+
+## Installation
+
+### 1. Homebrew (macOS / Linux)
+
+```bash
+brew install localstack/tap/lstk
+```
+
+### 2. NPM
+
+```bash
+npm install -g @localstack/lstk
+```
+
+### 3. Binaries
+Pre-built binaries are also available from [GitHub Releases](https://github.com/localstack/lstk/releases). 📦
+
+## Quick Start
+
+```sh
+lstk
+```
+
+Running `lstk` will automatically handle configuration setup and start LocalStack.
+
+## Features
+
+- **Start / stop / status** — manage LocalStack emulators with a single command
+- **Interactive TUI** — a Bubble Tea-powered terminal UI shown in an interactive terminal for commands like `start`, `login`, `status`, etc.
+- **Plain output** for CI/CD and scripting (auto-detected in non-interactive environments or forced with `--non-interactive`)
+- **Log streaming** — tail emulator logs in real-time with `--follow`; use `--verbose` to show all logs without filtering
+- **Snapshots** — save, load, and remove emulator state as local files, named cloud snapshots (`pod:` prefix), or in your own S3 bucket (`s3://`), and auto-load one on start
+- **Browser-based login** — authenticate via browser and store credentials securely in the system keyring
+- **AWS CLI profile** — optionally configure a `localstack` profile in `~/.aws/` after start
+- **Terraform integration** — proxy Terraform commands to LocalStack with automatic AWS provider endpoint configuration
+- **CDK integration** — proxy AWS CDK commands to LocalStack with automatic endpoint configuration (requires AWS CDK >= 2.177.0)
+- **Self-update** — check for and install the latest `lstk` release with `lstk update`
+- **Shell completions** — bash, zsh, and fish completions included
+
+## Authentication
+
+The CLI supports multiple auth workflows. `lstk` resolves your auth token in this order:
+
+1. **System keyring** — a token stored by a previous `lstk login`
+2. **`LOCALSTACK_AUTH_TOKEN` environment variable**
+3. **Browser login** — triggered automatically in interactive mode when neither of the above is present
+
+> [!NOTE]
+> If a keyring token exists, it takes precedence over `LOCALSTACK_AUTH_TOKEN`. Setting or changing the environment variable will have no effect until the keyring token is removed. Run `lstk logout` to clear the stored keyring token, after which the env var will be used.
+
+
+## Configuration
+
+`lstk` uses a TOML config file, created automatically on first run.
+
+`lstk` uses the first `config.toml` found in this order:
+1. `./.lstk/config.toml` (project-local)
+2. `$HOME/.config/lstk/config.toml`
+3. **macOS**: `$HOME/Library/Application Support/lstk/config.toml` / **Windows**: `%AppData%\lstk\config.toml`
+
+On first run, the config is created at `$HOME/.config/lstk/config.toml` if `$HOME/.config/` already exists, otherwise at the OS default (#3). This means #3 is only reached on macOS when `$HOME/.config/` didn't exist at first run.
+
+To see which config file is currently in use:
+
+```bash
+lstk config path
+```
+
+### Choosing an emulator
+
+`lstk` starts the AWS emulator by default. To run the Snowflake or Azure emulator instead, either select it interactively when prompted at start, or set the `type` in your config:
+
+```toml
+[[containers]]
+type = "azure"   # or "snowflake"
+port = "4566"
+```
+
+The chosen emulator must be running before you set up or use its CLI integration below.
+
+You can also configure cloud CLI integration:
+
+```bash
+lstk setup aws    # localstack profile in ~/.aws/
+lstk setup azure  # isolated Azure CLI config for `lstk az` (requires the Azure CLI)
+```
+
+After starting the Azure emulator and running `lstk setup azure`, run Azure CLI commands against LocalStack with `lstk az`:
+
+```bash
+lstk az group list
+```
+
+`lstk setup azure` registers a custom Azure cloud — pointing at LocalStack's endpoints — inside an isolated `AZURE_CONFIG_DIR`, so your global `~/.azure` keeps pointing at real Azure.
+
+To run existing `az` scripts unmodified against LocalStack, you can instead redirect your **global** Azure CLI:
+
+```bash
+lstk az start-interception   # plain `az` now targets LocalStack
+az group list                # hits LocalStack, no `lstk` prefix needed
+lstk az stop-interception    # back to real Azure (use --cloud to pick another cloud)
+```
+
+This is optional and changes global state affecting every `az` invocation until you stop it; prefer `lstk az <command>` unless a script must call plain `az`.
+
+You can also point `lstk` at a specific config file for any command:
+
+```bash
+lstk --config /path/to/config.toml start
+```
+
+### Default config
+
+```toml
+[[containers]]
+type = "aws"     # Emulator type. Currently supported: "aws", "snowflake", "azure"
+tag  = "latest"  # Docker image tag, e.g. "latest", "2026.03"
+port = "4566"    # Host port the emulator will be accessible on
+# volumes = []   # Bind mounts, "host:container[:ro]" (see below)
+# env = []       # Named environment profiles to apply (see [env.*] sections below)
+# snapshot = "pod:my-baseline"  # Snapshot REF auto-loaded on start (AWS only); see Snapshots below
+```
+
+**Fields:**
+- `type`: emulator type; one of `"aws"`, `"snowflake"`, or `"azure"`
+- `tag`: Docker image tag for LocalStack (e.g. `"latest"`, `"4.14.0"`); useful for pinning a version
+- `port`: port LocalStack listens on (default `4566`)
+- `volumes`: (optional) list of `"host:container[:ro]"` bind mounts, e.g. for init hooks or the persistent-state directory (see below)
+- `env`: (optional) list of named environment variable groups to inject into the container (see below)
+- `snapshot`: (optional) snapshot REF auto-loaded after the emulator starts on a fresh run — a local file path or a `pod:` cloud snapshot (see [Snapshots](#snapshots))
+
+### Passing environment variables to the container
+
+Define reusable named env sets and reference them per container:
+
+```toml
+[[containers]]
+type = "aws"
+tag  = "latest"
+port = "4566"
+env  = ["debug", "ci"]
+
+[env.debug]
+DEBUG = "1"
+ENFORCE_IAM = "1"
+PERSISTENCE = "1"
+
+[env.ci]
+SERVICES = "s3,sqs"
+EAGER_SERVICE_LOADING = "1"
+```
+
+Host environment variables prefixed with `LOCALSTACK_` are also forwarded to the emulator.
+
+### Mounting volumes and init hooks
+
+Use `volumes` to bind-mount host files or directories into the emulator, given as Docker-style `"host:container[:ro]"` strings. The most common use is [init hooks](https://docs.localstack.cloud/snowflake/capabilities/init-hooks/) — scripts LocalStack runs automatically on startup when mounted into `/etc/localstack/init/{boot,start,ready,shutdown}.d`:
+
+```toml
+[[containers]]
+type = "snowflake"
+port = "4566"
+volumes = ["./init.sf.sql:/etc/localstack/init/ready.d/init.sf.sql"]
+```
+
+- Relative host paths resolve against the config file's directory, and a leading `~/` is expanded.
+- Append `:ro` to mount read-only.
+- Host sources must already exist (init-hook entries are files, so `lstk` does not create them).
+
+#### Persistent state
+
+The persistent-state directory (mounted at `/var/lib/localstack`, managed by `lstk volume path` / `lstk volume clear`) defaults to the OS cache dir. Point it elsewhere with a `volumes` entry targeting that path:
+
+```toml
+volumes = ["/data:/var/lib/localstack"]
+```
+
+> The singular `volume = "..."` field is a legacy way to set only this directory. It still works, but `volumes` is preferred and is the only option for init hooks or other mounts.
+
+### Offline / enterprise environments
+
+`lstk start` degrades gracefully when the common enterprise blockers (Docker Hub unreachable, a forward proxy, TLS interception, or an unreachable license server) make a network request fail:
+
+- If the image cannot be pulled but is already present locally, `lstk` warns and starts the local image instead of failing.
+- If the license server cannot be reached, `lstk` skips its pre-flight check and lets the emulator validate its own bundled license at startup. A definitive rejection from the server (e.g. an invalid token) stays fatal.
+
+Pair this with a custom `image` in the config to point at a locally loaded image or an internal-registry mirror.
+
+## Interactive And Non-Interactive Mode
+
+`lstk` uses the TUI in an interactive terminal and plain output elsewhere. Use `--non-interactive` to force plain output even in a TTY:
+
+```bash
+lstk --non-interactive
+```
+
+## Logging
+
+`lstk` writes diagnostic logs to `lstk.log` in the same directory as the config file. The log file appends across runs and is automatically cleared when it exceeds 1 MB. Use `lstk config path` to print the full config file path; the log file lives alongside it in the same directory.
+
+## Environment Variables
+
+| Variable | Description |
+|---|---|
+| `LOCALSTACK_AUTH_TOKEN` | Auth token used for non-interactive runs or to skip browser login |
+| `LOCALSTACK_DISABLE_EVENTS=1` | Disables telemetry event reporting |
+| `LSTK_OTEL=1` | Enables OpenTelemetry trace export (disabled by default). When enabled, standard `OTEL_EXPORTER_OTLP_*` env vars are respected by the SDK (e.g. `OTEL_EXPORTER_OTLP_ENDPOINT` defaults to `http://localhost:4318`). Requires an OTLP-compatible backend to receive and visualize telemetry — for local development, `make otel` starts one (UI at http://localhost:16686). |
+| `DOCKER_HOST` | Override the Docker daemon socket (e.g. `unix:///home/user/.colima/default/docker.sock`). When unset, lstk tries the default socket and then probes common alternatives (Colima, OrbStack). |
+
+### Terraform Integration
+
+`lstk terraform` (alias `tf`) is a proxy that runs Terraform commands against LocalStack, automatically configuring the AWS provider to use LocalStack's endpoints. This allows you to test infrastructure-as-code locally before deploying to AWS.
+
+**lstk-specific flags** (appear after the `terraform`/`tf` subcommand):
+- `--region <region>` — Deployment region (default: `us-east-1`)
+- `--account <id>` — Target AWS account ID, 12 digits (default: `test`)
+
+**Environment variables:**
+- `LSTK_TF_CMD` — Terraform binary to invoke; default is `terraform` (e.g., use `tofu` for OpenTofu)
+- `LSTK_TF_OVERRIDE_FILE_NAME` — Override file name (default: `localstack_providers_override.tf`)
+- `LSTK_TF_DRY_RUN` — Generate the override file but do not run terraform
+- `AWS_ENDPOINT_URL` — Override the auto-resolved LocalStack endpoint
+- `AWS_REGION` — Fallback for `--region` flag
+- `AWS_ACCESS_KEY_ID` — Fallback for `--account` flag
+
+### CDK Integration
+
+`lstk cdk` is a proxy that runs AWS CDK commands against LocalStack, pointing the CDK CLI at LocalStack's endpoints via environment variables (so deploys target the running emulator instead of real AWS).
+
+**Requires AWS CDK CLI version 2.177.0 or newer** on your `PATH` (lstk targets LocalStack purely through environment variables, which older CDK versions ignore).
+
+**lstk-specific flags** (appear after the `cdk` subcommand):
+- `--region <region>` — Deployment region (default: `us-east-1`)
+
+CDK always targets the default LocalStack account 000000000000; there is no --account flag.
+
+**Environment variables:**
+- `LSTK_CDK_CMD` — CDK binary to invoke (default: `cdk`)
+- `AWS_ENDPOINT_URL` — Override the auto-resolved LocalStack endpoint
+- `AWS_ENDPOINT_URL_S3` — Override the auto-derived S3 endpoint
+- `AWS_REGION` — Fallback for `--region` flag
+
+## Usage
+
+```bash
+# Start the LocalStack emulator
+lstk
+
+# Start non-interactively (e.g. in CI)
+LOCALSTACK_AUTH_TOKEN=<token> lstk --non-interactive
+
+# Stop the running emulator
+lstk stop
+
+# Show emulator status and deployed resources
+lstk status
+
+# Stream emulator logs
+lstk logs --follow
+
+# Stream all emulator logs without filtering
+lstk logs --follow --verbose
+
+# Log in (opens browser for authentication)
+lstk login
+
+# Log out (removes stored credentials)
+lstk logout
+
+# Check whether a newer lstk version is available
+lstk update --check
+
+# Update lstk to the latest version
+lstk update
+
+# Show resolved config file path
+lstk config path
+
+# Set up AWS CLI profile integration
+lstk setup aws
+
+# Set up Azure CLI integration (isolated config for `lstk az`)
+lstk setup azure
+
+# Run Azure CLI commands against LocalStack
+lstk az group list
+
+# Or redirect your global `az` so existing scripts hit LocalStack unmodified
+lstk az start-interception
+lstk az stop-interception
+
+# Save emulator state to a local file
+lstk snapshot save ./my-snapshot.snapshot
+
+# Save emulator state as a named cloud snapshot on the LocalStack platform
+lstk snapshot save pod:my-baseline
+
+# Save to your own S3 bucket (credentials from AWS_* env vars or --profile)
+lstk snapshot save my-pod s3://my-bucket/prefix
+
+# Load a snapshot back into the running emulator
+lstk snapshot load pod:my-baseline
+lstk snapshot load my-pod s3://my-bucket/prefix
+
+# List cloud snapshots on the LocalStack platform (--all for the whole organization)
+lstk snapshot list
+
+# List snapshots in your own S3 bucket (requires a running emulator)
+lstk snapshot list s3://my-bucket/prefix
+
+# Show metadata for a single cloud snapshot
+lstk snapshot show pod:my-baseline
+
+# Delete a cloud snapshot (prompts for confirmation; --force to skip)
+lstk snapshot remove pod:my-baseline
+
+# Initialize Terraform with LocalStack
+lstk terraform init
+
+# Plan Terraform deployment in a specific region
+lstk terraform --region us-west-2 plan
+
+# Apply Terraform configuration (short form)
+lstk tf apply
+
+# Bootstrap and deploy an AWS CDK app against LocalStack
+lstk cdk bootstrap
+lstk cdk deploy --require-approval never
+
+# Synthesize a CDK app (offline, no running emulator needed)
+lstk cdk synth
+
+```
+
+## Snapshots
+
+Snapshots capture the running emulator's state so you can restore it later.
+
+A snapshot reference is a **local file**, a **cloud snapshot**, or an **S3 remote**:
+
+- **Local file** — an absolute or relative path. A `.snapshot` extension is added if omitted (snapshots saved as `.zip` by older lstk versions still load).
+- **Cloud snapshot** — a name with the `pod:` prefix (e.g. `pod:my-baseline`), stored on the LocalStack platform. Requires authentication (`LOCALSTACK_AUTH_TOKEN` or `lstk login`).
+- **S3 remote** — an `s3://bucket/prefix` location backed by your own S3 bucket. Supported by `save`, `load`, and `list`.
+
+```bash
+# Save (local, cloud, or S3)
+lstk snapshot save ./my-snapshot.snapshot
+lstk snapshot save pod:my-baseline
+lstk snapshot save my-pod s3://my-bucket/prefix
+
+# Load (starts the emulator first if needed)
+lstk snapshot load pod:my-baseline
+lstk snapshot load my-pod s3://my-bucket/prefix
+
+# List cloud snapshots — only your own by default, --all for the whole organization
+lstk snapshot list
+lstk snapshot list --all
+
+# List snapshots in an S3 bucket
+lstk snapshot list s3://my-bucket/prefix
+
+# Show metadata for a single cloud snapshot
+lstk snapshot show pod:my-baseline
+
+# Remove — cloud snapshots only; local files are never deleted by the CLI
+lstk snapshot remove pod:my-baseline          # prompts for confirmation
+lstk snapshot remove pod:my-baseline --force  # skip the prompt (required in non-interactive mode)
+```
+
+`lstk snapshot load` supports merge strategies via `--merge` (`account-region-merge` (default), `overwrite`, `service-merge`) to control how snapshot state combines with running state.
+
+### S3 remotes
+
+`save`, `load`, and `list` can target your own S3 bucket with an `s3://bucket/prefix` location. The pod name (the snapshot's identity within the bucket) is a positional argument separate from the `s3://` location — required for `load`, auto-generated for `save` when omitted, and unused for `list`.
+
+Credentials come from `AWS_ACCESS_KEY_ID` / `AWS_SECRET_ACCESS_KEY` (and optional `AWS_SESSION_TOKEN`), or from a named profile via `--profile <name>`. **Never put credentials in the URL** — lstk rejects an `s3://` ref that embeds them. lstk itself never touches S3: the running emulator performs the transfer, so these commands require a running emulator, and `list s3://…` queries the emulator rather than the LocalStack platform.
+
+```bash
+export AWS_ACCESS_KEY_ID=...
+export AWS_SECRET_ACCESS_KEY=...
+
+lstk snapshot save my-pod s3://my-bucket/prefix
+lstk snapshot load my-pod s3://my-bucket/prefix
+lstk snapshot list s3://my-bucket/prefix
+
+# Or read credentials from a named AWS profile instead of env vars
+lstk snapshot save my-pod s3://my-bucket/prefix --profile my-aws-profile
+```
+
+The S3 bucket must already exist — lstk checks up front and errors out rather than creating it on a typo. `remove` and `show` are not yet supported for S3 remotes.
+
+### Auto-load on start
+
+The AWS emulator can automatically load a snapshot whenever it starts. Set the `snapshot` field on its `[[containers]]` block to any snapshot reference — a local file or a `pod:` cloud snapshot:
+
+```toml
+[[containers]]
+type     = "aws"
+port     = "4566"
+snapshot = "pod:my-baseline"
+```
+
+Override or disable it for a single run without editing the config:
+
+```bash
+lstk start --snapshot pod:other-baseline  # load a different snapshot this run
+lstk start --no-snapshot                  # skip auto-loading this run
+```
+
+## Extensions
+
+lstk supports Git-style extensions: running `lstk <name>`, for a name that isn't a built-in command, delegates to an external `lstk-<name>` executable found on your `PATH`, forwarding all arguments and passing stdin/stdout/stderr through.
+
+```bash
+lstk my-tool --flag  # resolves and runs lstk-my-tool, if it exists
+```
+
+Extensions receive context about the current lstk setup (config dir, auth token, running emulators) via environment variables, so they can integrate without reimplementing discovery.
+
+See [docs/extensions-authoring.md](docs/extensions-authoring.md) for the extension contract and how to author your own.
+
+## Reporting bugs
+
+Feedback is welcome! Use the repository issue tracker for bug reports or feature requests.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@localstack/lstk_darwin_amd64",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "bin": {
     "lstk_darwin_amd64": "lstk"
   },
@@ -10,7 +10,10 @@
   "cpu": [
     "x64"
   ],
-  "files": [],
+  "files": [
+    "README.md",
+    "LICENSE"
+  ],
   "keywords": [
     "localstack",
     "cli",