docs(lstk): update CLI reference to v0.15.0#749
Conversation
Deploying localstack-docs with
|
| Latest commit: |
40ec6bc
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://169368e6.localstack-docs.pages.dev |
| Branch Preview URL: | https://claude-sleepy-ritchie-lvio4k.localstack-docs.pages.dev |
Bring the lstk CLI reference up to date with the current CLI surface (last documented around v0.12/v0.13, now v0.15.0): - Document the CLI/IaC proxy tools: az (+ start/stop-interception), terraform (tf), cdk, sam. - Add setup azure; correct setup aws (now has --force and a non-interactive mode, no longer interactive-only). - Add snapshot show and S3-remote support for snapshot save/load/list (--profile, credential precedence, running-emulator requirement). - Note snapshot now works for Snowflake/Azure with an experimental warning; only reset stays AWS-only. - Add global --snapshot/--no-snapshot flags and snapshot auto-load on start; document LOCALSTACK_ env forwarding. - Add config fields image, volumes, and snapshot; add a Volume mounts section. - Add an Extensions section. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QRmA1n8vtvoT3DnGQzRk87
9130fa3 to
02bc8e5
Compare
|
Not sure why @nik-localstack and @pinzon were added above[1] as reviewers. Cc @quetzalliwrites @remotesynth |
|
Cc @mmaureenliu for visibility |
|
@gtsiolis hey! the reason it pings the other two folks is because our codeowner's file is going to add the engineer service owner listed |
|
Ah, I see. But the file mentioned[1] has nothing to do with the change in this PR, maybe it's a fallback or I guess we don't have an engineer assigned for the |
|
I am ok with these changes, but I can't sign off until a PM owner approves for something important like @mmaureenliu may we get your ok on this one? :) (I will also ping her offline, as she may not see this comment on github, but in a slack dm she won't miss visibility) |
mmaureenliu
left a comment
There was a problem hiding this comment.
Great job! I've added a few comments, mostly clarification from user point view. Thanks for the great effort!
| | `--region <region>` | Deployment region (default `us-east-1`; falls back to `AWS_REGION`). | | ||
| | `--account <id>` | Target AWS account id, 12 digits (default `test`; falls back to `AWS_ACCESS_KEY_ID`). | | ||
|
|
||
| Commands that don't contact AWS (`fmt`, `validate`, `version`, and `init` when no S3 backend is declared) run without a running emulator; everything else requires the AWS emulator to be running and Docker healthy. |
There was a problem hiding this comment.
change "AWS" to "emulator" - this applies to all emulators.
- Drop legacy-CLI comparisons ("no per-tool wrapper", "mirroring v1's
AUTO_LOAD_POD") — how it works now, not the old xxx-local mapping.
- Defer the Extensions section (and its intro mention) until there is a
meaningful extension to document.
- Remove the duplicated intro note.
- Soften snapshot emulator-support framing: no top-level "AWS emulator
only" on the config field; note some snapshot features are fully
supported only on AWS for now and point to per-emulator docs.
- Reword "status resources" to "the resources listing in status".
- Volume mounts: fix the init-hook example to mount a script file (not a
directory), make it emulator-neutral, drop the untested read-only
mount, add an explanation, and link the per-emulator Initialization
Hooks guides.
- Azure interception: drop "second"/secondary framing and the line
steering users away from interception (it is the recommended mode).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QRmA1n8vtvoT3DnGQzRk87
|
Thanks @mmaureenliu! Pushed 40ec6bc addressing the review. Summary of what changed:
Two of your comments need a quick note back:
Generated by Claude Code |
|
hey @gtsiolis appreciate the quick addressing of Maureen's feedback, your reply is super detailed too. One thing, please make sure to resolve each feedback comment after you address them. Otherwise it can appear like it was missed and it's harder for the reviewer to track down each line item fixed. |
|
@mmaureenliu this is ready for you again! tyvm |
mmaureenliu
left a comment
There was a problem hiding this comment.
LGTM. I've asked the terraform question in #lstk channel and let's leave as is for now (I suspect you are right that our tflocal only supports aws). I did add an extra comment regarding a part not touched by current update, but is non-blocking.
|
|
||
| It depends on the emulator type configured in your `config.toml`. | ||
| The AWS emulator uses `localstack/localstack-pro`, the Snowflake emulator uses `localstack/snowflake`, and the Azure emulator uses `localstack/localstack-azure`. | ||
| All require a valid auth token (including the free Hobby tier). |
There was a problem hiding this comment.
Unrelated to current update, but I found this when I read the whole doc again - I think it's more correct to say "All require a valid license". An auth token only identifies the user and doesn't guarantee entitlement to product use, and if I remember correctly a registered user always has an auth token.
What
Brings the lstk CLI reference up to date with the current CLI surface. This is the first automated pass triggered by the
v0.15.0release, so it was a full audit of the live CLI (lstk --helpand every subcommand) against the doc rather than a single-release diff.The doc was last expanded around v0.12/v0.13 and had never documented several features that already shipped by then. This PR catches up the full backlog through v0.15.0.
Additions
az(incl.az start-interception/az stop-interception),terraform(aliastf),cdk, andsam: usage, the leading--region/--accountflags, offline-vs-running-emulator behavior, minimum tool versions, and supported env vars (AWS_ENDPOINT_URL,LSTK_TF_CMD,LSTK_SAM_CMD,LSTK_CDK_CMD, etc.).setup azure— isolatedAZURE_CONFIG_DIRsetup that routeslstk azto the Azure emulator.snapshot show— new subcommand (cloud-only).snapshot save/load/listnow accepts3://bucket/prefixwith a separate pod-name positional and a--profileflag; documented credential precedence and the running-emulator requirement forlist s3://….snapshotconfig field, plus global--snapshot <ref>/--no-snapshotflags.image(Docker image override),volumes(bind mounts) with a new Volume mounts section, andsnapshot.lstk-<name>dispatch and theLSTK_EXT_*runtime context.LOCALSTACK_-prefixed env vars are forwarded to the emulator on start.Corrections (stale content)
setup awsis no longer interactive-only: it now has a--forceflag and a non-interactive mode (writes the profile with defaults and exits 0). Removed the "requires an interactive terminal / no flag to auto-confirm" note.snapshotnow works for the Snowflake and Azure emulators too, with an experimental-support warning — it is no longer AWS-only. Onlyresetremains strictly AWS-only. Updated the "four subcommands" count to five.Needs a human eye
az/terraform/cdk/sam) and extensions are documented inline in the reference; if a fuller standalone guide is planned, these sections may want to link out to it later.Cc @localstack/devx for visibility and any corrections.
Generated by Claude Code