DOC-361: Migrate localstack CLI refs to lstk in Azure docs#803
Open
quetzalliwrites wants to merge 2 commits into
Open
DOC-361: Migrate localstack CLI refs to lstk in Azure docs#803quetzalliwrites wants to merge 2 commits into
quetzalliwrites wants to merge 2 commits into
Conversation
Replace azlocal's start-interception/stop-interception commands with lstk az across the Azure service pages and the az integration guide. azdlocal (azd.md) and azlocal's Python SDK (python.md) are left as-is since lstk has no equivalent for either.
quetzalliwrites
requested review from
HarshCasper and
remotesynth
as code owners
July 20, 2026 23:12
Deploying localstack-docs with
|
| Latest commit: |
42436ff
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0696a14f.localstack-docs.pages.dev |
| Branch Preview URL: | https://doc-361-migrate-all-localsta.localstack-docs.pages.dev |
mmaureenliu
requested changes
Jul 21, 2026
mmaureenliu
left a comment
mmaureenliu
left a comment
There was a problem hiding this comment.
Only one real change needed: similar to my comment on the quickstart, the az CLI doc should use the start/stop-interception as preferred mode.
I also notice there's still some lingering azlocal and azdlocal and have asked the team about them.
Lead with lstk az start-interception/stop-interception as the recommended default in the az integration guide, with the lstk setup azure + prefixed lstk az commands as an alternative. Drop the now-redundant interception notes in blob-storage and queue-storage that predate this recommendation.
Collaborator
Author
|
ready for you again @mmaureenliu 🐈⬛ |
mmaureenliu
approved these changes
Jul 23, 2026
mmaureenliu
left a comment
mmaureenliu
left a comment
There was a problem hiding this comment.
LGTM. Made a very minor nit-pick.
| $ lstk az stop-interception | ||
| ``` | ||
|
|
||
| The `az` CLI tool will now communicate with the Azure REST API on future invocations. |
There was a problem hiding this comment.
Though this is technically true, I think it's easier to comprehend if we say now it points to the real Azure cloud
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.
Summary
azlocal start-interception/stop-interceptionwithlstk az start-interception/lstk az stop-interceptionacross all 40 Azure service pages that use the interception workflow.integrations/az.mdto thelstk azpattern (lstk setup azureonce, then prefixazcommands withlstk az), matching the getting-started quickstart already updated in DOC-360.integrations/python.md: leftazlocal's Python SDK (PythonLocalSdk) as-is sincelstkhas no Python SDK equivalent, but added a note explaining the discrepancy with theazCLI examples elsewhere.integrations/azd.md: left untouched —azdlocal(theazd/Bicep wrapper) isn't somethinglstkproxies at all.Linear: https://linear.app/localstack/issue/DOC-361/migrate-all-localstack-cli-refs-to-lstk-in-azure-docs
Test plan
astro buildcompletes successfullystarlight-links-validatorreports all internal links validazlocal/localstackCLI refs outside the two intentionally-excluded files