Add lstk az start-interception and stop-interception commands#336
Merged
carole-lavillonniere merged 4 commits intoJun 24, 2026
Merged
Conversation
carole-lavillonniere
added
semver: minor
docs: needed
carole-lavillonniere
requested review from
anisaoshafi and
silv-io
as code owners
carole-lavillonniere
deleted the
cosy-761-add-lstk-az-start-interception-and-stop-interception
branch
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.
Motivation
lstk azpreviously only ran the Azure CLI against an isolatedAZURE_CONFIG_DIR, leaving global~/.azureuntouched. The Azure team and TGTM discussion agreedlstk azshould also offer azlocal's global pattern so existingazscripts run unmodified against LocalStack — and let the user choose.Changes
lstk az start-interception— registers and activates theLocalStackcloud in the user's global~/.azureso plainaz(any terminal/script) targets the LocalStack Azure emulator. Independent oflstk setup azure; does not touch global telemetry/survey prefs.lstk az stop-interception— switches the active cloud back toAzureCloud(override with--cloud <name>, validated against the liveaz cloud list) and re-enables instance discovery. Guarded: only changes the cloud whenLocalStackis still active, otherwise it reports and no-ops so it never clobbers an unrelated selection.Closes COSY-761