Skip to content

DOC-360: Update Azure getting started guide to use lstk#802

Open
quetzalliwrites wants to merge 2 commits into
mainfrom
doc-360-update-azure-getting-started-guide-to-use-lstk
Open

DOC-360: Update Azure getting started guide to use lstk#802
quetzalliwrites wants to merge 2 commits into
mainfrom
doc-360-update-azure-getting-started-guide-to-use-lstk

Conversation

@quetzalliwrites

@quetzalliwrites quetzalliwrites commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Replace the localstack CLI and azlocal wrapper across the Azure Getting Started docs (installation, auth-token, quickstart) with lstk, mirroring the AWS Getting Started guide.
  • installation.mdx: added an lstk section (install/configure-for-azure/start/update) as the recommended install path; removed the old localstack CLI subsection; Docker CLI/Compose kept as secondary options.
  • auth-token.mdx: replaced the "LocalStack CLI" auth subsection and troubleshooting mention with lstk's auth flow (LOCALSTACK_AUTH_TOKEN env var or lstk login).
  • quickstart.md: replaced azlocal start-interception/stop-interception with lstk setup azure + lstk az <command> prefixing. Native az CLI commands and the az CLI prerequisite are unchanged.

Linear: https://linear.app/localstack/issue/DOC-360/update-azure-getting-started-guide-to-use-lstk

Test plan

  • astro build completes successfully
  • starlight-links-validator reports all internal links and anchors valid

Replace the localstack CLI and azlocal wrapper across the Azure Getting
Started docs with lstk, mirroring the AWS Getting Started guide.
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 20, 2026

Copy link
Copy Markdown

Deploying localstack-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: f3bc634
Status: ✅  Deploy successful!
Preview URL: https://53a64ba8.localstack-docs.pages.dev
Branch Preview URL: https://doc-360-update-azure-getting.localstack-docs.pages.dev

View logs

@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.

Thanks! I've left some comments mostly highlighting where things are done differently for the Azure emulator.

Comment thread src/content/docs/azure/getting-started/auth-token.mdx
Comment thread src/content/docs/azure/getting-started/auth-token.mdx Outdated
Comment thread src/content/docs/azure/getting-started/index.mdx Outdated
### Configure lstk for Azure

You can start the Azure emulator using the following methods:
`lstk` starts the AWS emulator by default. To target the Azure emulator instead, create a project-local `.lstk/config.toml`:

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

That's no longer true. If user starts lstk for the first time it will ask you to pick an emulator and record your choice in the global config as the default. So I'd move this section below "Update lstk" and frame it as "What to do if you already use lstk and your global config defaults to the AWS emulator"

Comment thread src/content/docs/azure/getting-started/index.mdx Outdated
Comment thread src/content/docs/azure/getting-started/quickstart.md Outdated
Comment thread src/content/docs/azure/getting-started/quickstart.md
Comment thread src/content/docs/azure/getting-started/quickstart.md Outdated
- Simplify the auth-token lstk section: just run lstk/lstk start,
  since lstk resolves the token automatically; drop manual env var
  instructions in favor of lstk login for credential issues.
- Reorder the installation intro to lead with the lstk recommendation
  (mirroring the AWS getting started guide), and move the manual
  per-project config.toml override below Update lstk, framed as an
  edge case for users whose global config already defaults elsewhere.
  Note that the first lstk run also prompts for an emulator choice.
- Quickstart: recommend lstk az start-interception/stop-interception
  as the default flow (plain az commands in between), with
  lstk setup azure + prefixed lstk az commands as the alternative.
  Add explicit lstk start/stop steps.
@quetzalliwrites

Copy link
Copy Markdown
Collaborator Author

ready for you again @mmaureenliu !

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.

2 participants