docs(lstk hotfix): update CLI reference to v0.16.0#788
Merged
Conversation
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>
- 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>
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>
gtsiolis
requested review from
HarshCasper,
quetzalliwrites and
remotesynth
as code owners
quetzalliwrites
approved these changes
Jul 15, 2026
quetzalliwrites
changed the title
hotfix): update CLI reference to v0.16.0
Collaborator
|
ty for fixing the prev PR @gtsiolis! appreciate your ownership mindset 💪🏻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Re-opens the lstk CLI reference update (originally #774) against
mainso it can be merged as the intended release-independent hotfix.#774 accidentally merged into
aws-docs-release-augustafter its base branch was changed mid-merge; that merge is being reverted in #787. This PR restores the original setup — the same reviewed branch (claude/wonderful-lovelace-f8t49h, all review feedback from @mmaureenliu and @quetzalliwrites already applied) targetingmain.The diff is unchanged from #774 (single file,
lstk.mdx) andmainhasn't touched that file, so it merges cleanly.Note for reviewers
The Validate Refs check will be red here because the head branch isn't named
aws-docs-*/snowflake-docs-*, which that policy requires for merges intomain. This is expected for the hotfix-to-mainflow — please don't retarget the base to make it green (retargeting mid-merge is exactly what sent #774 to the wrong branch). @quetzalliwrites to merge via the usual hotfix path.cc @quetzalliwrites @localstack/devx
Generated by Claude Code