Skip to content

Mention the lstk CLI in the localstack CLI docs#700

Open
gtsiolis wants to merge 5 commits into
mainfrom
pro-312-mention-lstk-cli-in-localstack-cli-docs
Open

Mention the lstk CLI in the localstack CLI docs#700
gtsiolis wants to merge 5 commits into
mainfrom
pro-312-mention-lstk-cli-in-localstack-cli-docs

Conversation

@gtsiolis

@gtsiolis gtsiolis commented Jun 12, 2026

Copy link
Copy Markdown
Member

Summary

Adds a short note to the top of the LocalStack CLI reference pointing readers to lstk, our new Go-based CLI, and updates the lstk page itself — keeping its positioning lstk-only and addressing the review feedback left on it.

It also replaces the auto-generated "This documentation was auto-generated from LocalStack CLI version " note, which wasn't useful and was reliably out of date. That version is captured only when the monthly update-cli-docs workflow runs (the 15th), so it always trails the actual release — the page read 2026.4.0 while 2026.5.x had been on PyPI for weeks (2026.5.0 shipped 5 days after the last regeneration). A stamp that's accurate for ~1 day a month is worse than none.

Changes

The LocalStack CLI page is auto-generated by scripts/generate_cli_docs.py, so that change is made in the generator and mirrored into the current output:

  • scripts/generate_cli_docs.py — replace the version provenance :::note with a pointer to lstk; remove the now-dead version plumbing (the localstack --version call + unused parameter).
  • localstack-cli.md — the regenerated note.
  • lstk.mdx — update the top note to reflect that lstk covers lifecycle, monitoring, and storage (snapshot), and remove the "difference between lstk and the localstack CLI" FAQ so the page stays focused on lstk (the localstack CLI is being deprecated).

Rendered notes:

LocalStack CLI page: lstk is our new Go-based CLI with an interactive terminal UI for lifecycle (start, stop), monitoring (status, logs), storage (snapshot), and more.

lstk page: lstk covers the everyday emulator workflow: lifecycle (start, stop), monitoring (status, logs), storage (snapshot), and more.

Follow-up

Documenting the lstk snapshot command in detail and the terraform/az/setup proxy commands is tracked separately and will land in its own PR.

Fix PRO-312

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 12, 2026

Copy link
Copy Markdown

Deploying localstack-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 36ef67b
Status: ✅  Deploy successful!
Preview URL: https://64d29bef.localstack-docs.pages.dev
Branch Preview URL: https://pro-312-mention-lstk-cli-in.localstack-docs.pages.dev

View logs

@gtsiolis gtsiolis force-pushed the pro-312-mention-lstk-cli-in-localstack-cli-docs branch from 4be89f2 to 83eab98 Compare June 12, 2026 11:27
@quetzalliwrites

Copy link
Copy Markdown
Collaborator

cc @mmaureenliu for visibility since she is just now logging tickets for this doc too :)

@gtsiolis gtsiolis self-assigned this Jun 12, 2026
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk.mdx Outdated
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk.mdx Outdated
gtsiolis and others added 3 commits June 16, 2026 12:39
The Developer Tools restructure (#691) moved the localstack-cli and lstk
pages under /aws/developer-tools/running-localstack/. Update the cross-links
in the generated CLI doc, its generator, and the lstk FAQ to match.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@gtsiolis gtsiolis force-pushed the pro-312-mention-lstk-cli-in-localstack-cli-docs branch from 83eab98 to e22353c Compare June 16, 2026 09:43
Keep the lstk doc focused only on lstk. With the localstack CLI being
deprecated, the doc shouldn't compare against it or highlight features
(Extensions, Ephemeral Instances) that lstk won't add. Discoverability of
lstk still flows from the localstack CLI page note, which is unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@gtsiolis

Copy link
Copy Markdown
Member Author

Can someone take another look? 👀

@mmaureenliu mmaureenliu left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did a complete re-read of the entire article and left quite a few comments/questions. None are blocking so I've approved already, but I do want them addressed at some point.

Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk.mdx Outdated
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk.mdx Outdated
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk.mdx Outdated
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk.mdx
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk.mdx Outdated
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk.mdx
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk.mdx
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk.mdx Outdated
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk.mdx Outdated
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk.mdx Outdated
- Prerequisites: require a license (not just an Auth Token); lstk handles auth
- Quick start: simplify the auth wording
- CI: use a CI Auth Token, linked to the CI auth-token docs
- Config: document the snowflake/azure emulator types and per-project emulator config
- MAIN_CONTAINER_NAME: clarify it is derived and not configurable
- FAQ: "require a license" instead of "auth token"
- Troubleshooting: link the corporate-proxy FAQ; point "Getting help" to Get Help

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@gtsiolis

Copy link
Copy Markdown
Member Author

Thanks for taking a closer look, @mmaureenliu! Addressed comments in 36ef67b.
It should be good to merge, so we can focus on #701.

Could a CODEOWNER approve this to unblock merging this and moving to #701? Cc @quetzalliwrites @remotesynth

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants