| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Deploying localstack-docs with
|
| Latest commit: | 076b02c |
| Status: | ✅ Deploy successful! |
| Preview URL: | https://65d8c703.localstack-docs.pages.dev |
| Branch Preview URL: | https://claude-wonderful-lovelace-f8.localstack-docs.pages.dev |
Sorry, something went wrong.
Bring the lstk CLI reference up to date with releases v0.14.0 through v0.16.0 (doc previously reflected ~v0.13.0). Changes: - Document the Azure CLI proxy (lstk az) with global interception, and the IaC tool proxies lstk terraform (alias tf), lstk cdk, and lstk sam. - Add lstk setup azure and correct lstk setup aws: it now runs non-interactively (writes defaults) and gained a --force flag. - Remove the deleted lstk config profile command. - Document snapshot show, S3 remotes for save/load/list, and that snapshot save/load now work (experimentally) for Snowflake and Azure. - Document snapshot auto-load on start (snapshot config field, --snapshot / --no-snapshot flags). - Add config fields image, volumes, and snapshot; add Custom container image and Volume mounts sections. - Add global flags --json, --snapshot, --no-snapshot. - Add Offline and enterprise environments and Extensions sections. - Document LOCALSTACK_CLIENT_NAME/VERSION injected vars and GATEWAY_LISTEN host exposure. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@mmaureenliu could you take a look? |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for the effort!
Sorry, something went wrong.
- Intro: drop the "*local wrapper" phrasing; say tools run directly. - Emulator types: clarify the default aws emulator is used non-interactively only when no config file is found; drop snapshot from the AWS-only command list (it now works for all emulators). - az interception caution: soften "Prefer" to "Use" to match the Azure docs, which treat interception as the preferred mode. - terraform: note that lstk terraform currently targets AWS only. - Remove the Extensions section (deferred). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Thanks for the review! Addressed the feedback in bdf0a8e:
One I left as-is: the intro/notes duplication (L17) — you wanted @quetzalliwrites's take first, so I haven't touched it pending that. Generated by Claude Code |
Sorry, something went wrong.
Delete the introductory note component and keep only its tool-proxy sentence as a plain paragraph, per review feedback (the first sentence duplicated the lifecycle description above). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Done in f5b86f7 — deleted the intro note component and kept only its second sentence (the tool-proxy list) as a plain paragraph. That was the last open item from the review; all threads should now be addressed. Thanks @quetzalliwrites, @mmaureenliu! Generated by Claude Code |
Sorry, something went wrong.
|
Small heads-up on the dash→parenthesis change (intro, line 18): the closing em-dash was doing double duty as the clause separator, so the sentence now needs a comma after the parenthesis:
Happy to push that one-character fix if you'd prefer, or leave it to your style pass — your call, @quetzalliwrites. Generated by Claude Code |
Sorry, something went wrong.
|
ty @gtsiolis for your contribution, you always place such detailed thought into each PR 🌈 |
Sorry, something went wrong.
|
@gtsiolis let me get back to you before eod on merging this PR, i agree this can/should go live before end of month july aws release |
Sorry, something went wrong.
|
merging as a hotfix since this is not aws release dependent |
Sorry, something went wrong.
|
@gtsiolis Holaaa George, a quick reminder regarding PR coordination: When I am actively preparing PRs and managing branch movements, do not make mid-process updates to those branches. Your recent update accidentally caused this PR to merge into the August release branch instead of main. I know you were likely trying to fix it thinking I mistakenly targetted the main branch, but it disrupted the release flow, and I now have to revert and restart the process. Moving forward, if you see me actively working on or merging docs PRs, check in with me before making any adjustments so we don't override active work. Thanks for understanding. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
Brings the lstk CLI reference up to date with the current CLI. The doc previously reflected roughly v0.13.0 (last meaningfully expanded in localstack-docs #701, merged 2026-06-24). This PR catches up the full backlog through the latest release, v0.16.0 — covering v0.14.0, v0.14.1, v0.15.0, and v0.16.0.
Rather than trust a diff, I walked the live CLI surface (lstk --help and every subcommand's --help, plus the config/env source), so this flags stale content as well as additions.
New commands / features documented
Stale content corrected
Notes for reviewers
Cc @localstack/devx for visibility and any corrections.