From fffaf2522b4fb9c485a78a5d3f566d8040bdf90a Mon Sep 17 00:00:00 2001 From: Quetzalli Date: Tue, 21 Jul 2026 01:11:34 +0200 Subject: [PATCH 1/3] DOC-361: Migrate localstack CLI refs to lstk in Azure docs 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. --- src/content/docs/azure/integrations/az.md | 41 ++++--------------- src/content/docs/azure/integrations/python.md | 5 +++ .../docs/azure/services/action-group.mdx | 4 +- .../docs/azure/services/api-management.mdx | 6 +-- .../azure/services/application-insights.mdx | 4 +- .../docs/azure/services/autoscale-setting.mdx | 4 +- .../docs/azure/services/bastion-host.mdx | 6 +-- .../docs/azure/services/blob-storage.mdx | 10 ++--- .../azure/services/container-instance.mdx | 6 +-- .../azure/services/container-registry.mdx | 4 +- src/content/docs/azure/services/cosmos-db.mdx | 4 +- .../azure/services/data-collection-rules.mdx | 4 +- .../docs/azure/services/dbfor-postgresql.mdx | 6 +-- .../azure/services/diagnostic-setting.mdx | 4 +- .../docs/azure/services/front-door.mdx | 6 +-- .../docs/azure/services/functions-app.mdx | 4 +- src/content/docs/azure/services/key-vault.mdx | 6 +-- .../docs/azure/services/log-analytics.mdx | 4 +- .../docs/azure/services/managed-identity.mdx | 6 +-- .../docs/azure/services/metric-alert.mdx | 4 +- src/content/docs/azure/services/monitor.mdx | 6 +-- .../docs/azure/services/nat-gateway.mdx | 6 +-- .../docs/azure/services/network-interface.mdx | 6 +-- .../docs/azure/services/private-dns-zone.mdx | 6 +-- .../docs/azure/services/private-endpoint.mdx | 6 +-- .../docs/azure/services/public-ip-address.mdx | 6 +-- .../docs/azure/services/public-ip-prefix.mdx | 6 +-- .../docs/azure/services/queue-storage.mdx | 8 ++-- .../docs/azure/services/resource-graph.mdx | 6 +-- .../docs/azure/services/resource-manager.mdx | 6 +-- .../docs/azure/services/role-assignment.mdx | 4 +- .../docs/azure/services/role-definition.mdx | 4 +- .../docs/azure/services/route-table.mdx | 6 +-- .../azure/services/scheduled-query-rules.mdx | 4 +- .../azure/services/service-bus-data-plane.mdx | 6 +-- .../docs/azure/services/service-bus.mdx | 6 +-- src/content/docs/azure/services/sql.mdx | 6 +-- .../docs/azure/services/storage-accounts.mdx | 6 +-- .../docs/azure/services/table-storage.mdx | 6 +-- .../docs/azure/services/virtual-network.mdx | 6 +-- src/content/docs/azure/services/web-app.mdx | 6 +-- src/content/docs/azure/services/web-test.mdx | 4 +- src/content/docs/azure/services/workbook.mdx | 4 +- 43 files changed, 124 insertions(+), 144 deletions(-) diff --git a/src/content/docs/azure/integrations/az.md b/src/content/docs/azure/integrations/az.md index 63e498cf..9ab1418c 100644 --- a/src/content/docs/azure/integrations/az.md +++ b/src/content/docs/azure/integrations/az.md @@ -16,58 +16,33 @@ This guide will show you how to use it to interact with LocalStack. This guide is designed for users who are new to LocalStack for Azure emulator and assumes basic knowledge of how the Azure CLI works. We will demonstrate how to create, show and delete an Azure resource group. -### Install the packages +### Prerequisites -Run the following command to install the required packages: +This guide uses [`lstk`](/aws/developer-tools/running-localstack/lstk/), which proxies your host `az` CLI against the Azure emulator using an isolated configuration directory, so your global `~/.azure` setup is left untouched. -``` -$ pip install azlocal -``` - -You now have access to the following LocalStack tools: - -| CLI tool | LocalStack tool | Purpose | -|-----------|-----------------|-------------------------------| -| az | azlocal | Interact with Azure resources | -| azd | azdlocal | Deploy ARM/Bicep templates | - -The LocalStack variants are wrappers around the existing tools, so you keep the full functionality of the original tool. It will just redirect all commands to the running LocalStack Emulator. - -### Setup the az CLI - -To make sure the `az` tool sends requests to the Azure Emulator REST API, run the following command: +Run the following command once to prepare the integration: ``` -$ azlocal start_interception +$ lstk setup azure ``` ### Create and manage the Resource Group -Run the following command to create a resource group in the Emulator: +Run the following command to create a resource group in the Emulator, prefixing the same `az` command you would normally run with `lstk az`: ``` -$ az group create --name MyResourceGroup --location westeurope +$ lstk az group create --name MyResourceGroup --location westeurope ``` To check the resource group details, run the following command: ``` -$ az group show --name MyResourceGroup +$ lstk az group show --name MyResourceGroup ``` To delete the resource group, run the following command: ``` -$ az group delete --name MyResourceGroup --yes +$ lstk az group delete --name MyResourceGroup --yes ``` -### Teardown - -When you're done using the Azure Emulator, you can run the following command: - -``` -$ azlocal stop_interception -``` - -The `az` CLI tool will now communicate with the Azure REST API on future invocations. - diff --git a/src/content/docs/azure/integrations/python.md b/src/content/docs/azure/integrations/python.md index 8e99d6a2..dbeac0a2 100644 --- a/src/content/docs/azure/integrations/python.md +++ b/src/content/docs/azure/integrations/python.md @@ -29,6 +29,11 @@ The `azlocal` package is provided by LocalStack to simplify the process of inter The other two packages are packages provided by Azure to interact with Azure services in Python. +:::note +Elsewhere in these docs, `az` CLI examples use [`lstk az`](/aws/developer-tools/running-localstack/lstk/) instead of `azlocal`. +`lstk` proxies the `az` CLI, but does not provide a Python SDK interception helper — for Python, `azlocal`'s `PythonLocalSdk` (used below) remains the supported approach. +::: + ### Create a Python file You can now use the Azure SDK for Python to interact with LocalStack. diff --git a/src/content/docs/azure/services/action-group.mdx b/src/content/docs/azure/services/action-group.mdx index 76df0355..03bd066c 100644 --- a/src/content/docs/azure/services/action-group.mdx +++ b/src/content/docs/azure/services/action-group.mdx @@ -22,14 +22,14 @@ This guide walks you through creating an Action Group with an email receiver and Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/api-management.mdx b/src/content/docs/azure/services/api-management.mdx index 1bd050ef..89998e7f 100644 --- a/src/content/docs/azure/services/api-management.mdx +++ b/src/content/docs/azure/services/api-management.mdx @@ -18,19 +18,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide walks you through creating an API Management service, adding an API, and defining and updating an operation. It is designed for users new to API Management and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide walks you through creating an API Management service, adding an API, and defining and updating an operation. It is designed for users new to API Management and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/application-insights.mdx b/src/content/docs/azure/services/application-insights.mdx index b656b497..8b123d51 100644 --- a/src/content/docs/azure/services/application-insights.mdx +++ b/src/content/docs/azure/services/application-insights.mdx @@ -23,14 +23,14 @@ The Azure CLI commands below use the [`application-insights` extension](https:// Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/autoscale-setting.mdx b/src/content/docs/azure/services/autoscale-setting.mdx index 0de5306f..bb2bea85 100644 --- a/src/content/docs/azure/services/autoscale-setting.mdx +++ b/src/content/docs/azure/services/autoscale-setting.mdx @@ -22,14 +22,14 @@ This guide walks you through creating an autoscale setting targeting an App Serv Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/bastion-host.mdx b/src/content/docs/azure/services/bastion-host.mdx index 938a15d5..60c0f0c2 100644 --- a/src/content/docs/azure/services/bastion-host.mdx +++ b/src/content/docs/azure/services/bastion-host.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Bastion Host and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Bastion Host and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/blob-storage.mdx b/src/content/docs/azure/services/blob-storage.mdx index 08a2d891..e70a956d 100644 --- a/src/content/docs/azure/services/blob-storage.mdx +++ b/src/content/docs/azure/services/blob-storage.mdx @@ -15,23 +15,23 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Blob Storage and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Blob Storage and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` :::note -As an alternative to using the `azlocal` CLI, users can run: +As an alternative to using the `lstk az` proxy, users can run: -`azlocal start-interception` +`lstk az start-interception` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator REST API. To revert this configuration, run: -`azlocal stop-interception` +`lstk az stop-interception` This reconfigures the `az` CLI to send commands to the official Azure management REST API ::: diff --git a/src/content/docs/azure/services/container-instance.mdx b/src/content/docs/azure/services/container-instance.mdx index f77c08df..6ee9f8d6 100644 --- a/src/content/docs/azure/services/container-instance.mdx +++ b/src/content/docs/azure/services/container-instance.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Container Instances and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Container Instances and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/container-registry.mdx b/src/content/docs/azure/services/container-registry.mdx index 4d490995..68381195 100644 --- a/src/content/docs/azure/services/container-registry.mdx +++ b/src/content/docs/azure/services/container-registry.mdx @@ -22,14 +22,14 @@ This guide walks you through creating a registry, logging in with Docker, pushin Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/cosmos-db.mdx b/src/content/docs/azure/services/cosmos-db.mdx index be126fec..112a36ef 100644 --- a/src/content/docs/azure/services/cosmos-db.mdx +++ b/src/content/docs/azure/services/cosmos-db.mdx @@ -22,14 +22,14 @@ This guide walks you through creating Cosmos DB accounts, databases, and contain Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/data-collection-rules.mdx b/src/content/docs/azure/services/data-collection-rules.mdx index 79777217..2eccd38e 100644 --- a/src/content/docs/azure/services/data-collection-rules.mdx +++ b/src/content/docs/azure/services/data-collection-rules.mdx @@ -22,14 +22,14 @@ This guide walks you through creating a Data Collection Endpoint, a Data Collect Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/dbfor-postgresql.mdx b/src/content/docs/azure/services/dbfor-postgresql.mdx index 1a0dac62..1ed764c8 100644 --- a/src/content/docs/azure/services/dbfor-postgresql.mdx +++ b/src/content/docs/azure/services/dbfor-postgresql.mdx @@ -15,19 +15,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Azure DB for PostgreSQL and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Azure DB for PostgreSQL and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/diagnostic-setting.mdx b/src/content/docs/azure/services/diagnostic-setting.mdx index ae0bdc20..1f9af6d4 100644 --- a/src/content/docs/azure/services/diagnostic-setting.mdx +++ b/src/content/docs/azure/services/diagnostic-setting.mdx @@ -23,14 +23,14 @@ See also the [Monitor](/azure/services/monitor) page for a broader overview of d Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/front-door.mdx b/src/content/docs/azure/services/front-door.mdx index 8060f370..07dbcd55 100644 --- a/src/content/docs/azure/services/front-door.mdx +++ b/src/content/docs/azure/services/front-door.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Azure Front Door and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Azure Front Door and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/functions-app.mdx b/src/content/docs/azure/services/functions-app.mdx index c2361059..05949194 100644 --- a/src/content/docs/azure/services/functions-app.mdx +++ b/src/content/docs/azure/services/functions-app.mdx @@ -22,14 +22,14 @@ This guide walks you through creating a Function App backed by a Storage Account Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/key-vault.mdx b/src/content/docs/azure/services/key-vault.mdx index 6f728c36..2055f69f 100644 --- a/src/content/docs/azure/services/key-vault.mdx +++ b/src/content/docs/azure/services/key-vault.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Key Vault and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Key Vault and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/log-analytics.mdx b/src/content/docs/azure/services/log-analytics.mdx index 400d5551..963b9b50 100644 --- a/src/content/docs/azure/services/log-analytics.mdx +++ b/src/content/docs/azure/services/log-analytics.mdx @@ -22,14 +22,14 @@ This guide walks you through creating a Log Analytics Workspace, retrieving its Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/managed-identity.mdx b/src/content/docs/azure/services/managed-identity.mdx index 74bd8c31..ba710c4c 100644 --- a/src/content/docs/azure/services/managed-identity.mdx +++ b/src/content/docs/azure/services/managed-identity.mdx @@ -20,19 +20,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Managed Identity and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Managed Identity and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/metric-alert.mdx b/src/content/docs/azure/services/metric-alert.mdx index 7dda44c1..c09990ab 100644 --- a/src/content/docs/azure/services/metric-alert.mdx +++ b/src/content/docs/azure/services/metric-alert.mdx @@ -22,14 +22,14 @@ This guide walks you through creating a metric alert rule referencing an action Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/monitor.mdx b/src/content/docs/azure/services/monitor.mdx index f24f8a5a..33102c27 100644 --- a/src/content/docs/azure/services/monitor.mdx +++ b/src/content/docs/azure/services/monitor.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Azure Monitor and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Azure Monitor and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/nat-gateway.mdx b/src/content/docs/azure/services/nat-gateway.mdx index 6cf8bc19..450bb026 100644 --- a/src/content/docs/azure/services/nat-gateway.mdx +++ b/src/content/docs/azure/services/nat-gateway.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to NAT Gateway and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to NAT Gateway and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/network-interface.mdx b/src/content/docs/azure/services/network-interface.mdx index 89e6b5e4..06304dcd 100644 --- a/src/content/docs/azure/services/network-interface.mdx +++ b/src/content/docs/azure/services/network-interface.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Network Interfaces and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Network Interfaces and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/private-dns-zone.mdx b/src/content/docs/azure/services/private-dns-zone.mdx index d7c1c0a9..d5d77b92 100644 --- a/src/content/docs/azure/services/private-dns-zone.mdx +++ b/src/content/docs/azure/services/private-dns-zone.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Private DNS Zone and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Private DNS Zone and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/private-endpoint.mdx b/src/content/docs/azure/services/private-endpoint.mdx index 762edd30..55c8e6ad 100644 --- a/src/content/docs/azure/services/private-endpoint.mdx +++ b/src/content/docs/azure/services/private-endpoint.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Private Endpoint and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Private Endpoint and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/public-ip-address.mdx b/src/content/docs/azure/services/public-ip-address.mdx index 4a85e287..67733c2e 100644 --- a/src/content/docs/azure/services/public-ip-address.mdx +++ b/src/content/docs/azure/services/public-ip-address.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Public IP Addresses and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Public IP Addresses and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/public-ip-prefix.mdx b/src/content/docs/azure/services/public-ip-prefix.mdx index f7c9177e..e8555418 100644 --- a/src/content/docs/azure/services/public-ip-prefix.mdx +++ b/src/content/docs/azure/services/public-ip-prefix.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Public IP Prefixes and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Public IP Prefixes and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/queue-storage.mdx b/src/content/docs/azure/services/queue-storage.mdx index 940df097..146c6f27 100644 --- a/src/content/docs/azure/services/queue-storage.mdx +++ b/src/content/docs/azure/services/queue-storage.mdx @@ -17,17 +17,17 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Queue Storage and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Queue Storage and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` :::note -`azlocal start-interception` points the Azure CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. -To revert this configuration, run `azlocal stop-interception` so the CLI targets the official Azure management REST API again. +`lstk az start-interception` points the Azure CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. +To revert this configuration, run `lstk az stop-interception` so the CLI targets the official Azure management REST API again. ::: ### Create a resource group diff --git a/src/content/docs/azure/services/resource-graph.mdx b/src/content/docs/azure/services/resource-graph.mdx index a7a7e0d0..b47b9ddd 100644 --- a/src/content/docs/azure/services/resource-graph.mdx +++ b/src/content/docs/azure/services/resource-graph.mdx @@ -17,19 +17,19 @@ LocalStack for Azure enables users to explore resources deployed within the loca ## Getting started -This guide is designed for users new to Resource Graph and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Resource Graph and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/resource-manager.mdx b/src/content/docs/azure/services/resource-manager.mdx index e3decd43..ca7b66b5 100644 --- a/src/content/docs/azure/services/resource-manager.mdx +++ b/src/content/docs/azure/services/resource-manager.mdx @@ -20,19 +20,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Resource Manager and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Resource Manager and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/role-assignment.mdx b/src/content/docs/azure/services/role-assignment.mdx index f2f1dd87..6f126fb2 100644 --- a/src/content/docs/azure/services/role-assignment.mdx +++ b/src/content/docs/azure/services/role-assignment.mdx @@ -22,14 +22,14 @@ This guide walks you through assigning a built-in role to a managed identity, li Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/role-definition.mdx b/src/content/docs/azure/services/role-definition.mdx index 9e3a7b18..d7944158 100644 --- a/src/content/docs/azure/services/role-definition.mdx +++ b/src/content/docs/azure/services/role-definition.mdx @@ -22,14 +22,14 @@ This guide walks you through creating a custom role definition, listing role def Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/route-table.mdx b/src/content/docs/azure/services/route-table.mdx index 8e3fe734..ee53c254 100644 --- a/src/content/docs/azure/services/route-table.mdx +++ b/src/content/docs/azure/services/route-table.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Route Tables and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Route Tables and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/scheduled-query-rules.mdx b/src/content/docs/azure/services/scheduled-query-rules.mdx index 5891696e..100b506c 100644 --- a/src/content/docs/azure/services/scheduled-query-rules.mdx +++ b/src/content/docs/azure/services/scheduled-query-rules.mdx @@ -22,14 +22,14 @@ This guide walks you through creating a Scheduled Query Rule that targets a Log Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/service-bus-data-plane.mdx b/src/content/docs/azure/services/service-bus-data-plane.mdx index 82e10cd4..7e1f9afe 100644 --- a/src/content/docs/azure/services/service-bus-data-plane.mdx +++ b/src/content/docs/azure/services/service-bus-data-plane.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Service Bus Data Plane APIs and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Service Bus Data Plane APIs and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/service-bus.mdx b/src/content/docs/azure/services/service-bus.mdx index bf00e3cd..bdba2e34 100644 --- a/src/content/docs/azure/services/service-bus.mdx +++ b/src/content/docs/azure/services/service-bus.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Service Bus and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Service Bus and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/sql.mdx b/src/content/docs/azure/services/sql.mdx index 3afc783a..6871f2df 100644 --- a/src/content/docs/azure/services/sql.mdx +++ b/src/content/docs/azure/services/sql.mdx @@ -17,19 +17,19 @@ The supported APIs are listed in the [API Coverage](#api-coverage) section. ## Getting started -This guide is designed for users new to Azure SQL Database and assumes basic knowledge of the Azure CLI and `azlocal`. The following example creates a SQL server and database, configures firewall access, and defines retention and encryption settings. +This guide is designed for users new to Azure SQL Database and assumes basic knowledge of the Azure CLI and `lstk az`. The following example creates a SQL server and database, configures firewall access, and defines retention and encryption settings. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/storage-accounts.mdx b/src/content/docs/azure/services/storage-accounts.mdx index cfca6deb..0f67bd4f 100644 --- a/src/content/docs/azure/services/storage-accounts.mdx +++ b/src/content/docs/azure/services/storage-accounts.mdx @@ -20,19 +20,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Azure Storage Accounts and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Azure Storage Accounts and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/table-storage.mdx b/src/content/docs/azure/services/table-storage.mdx index 6553f5df..d9d18a41 100644 --- a/src/content/docs/azure/services/table-storage.mdx +++ b/src/content/docs/azure/services/table-storage.mdx @@ -17,19 +17,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Table Storage and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Table Storage and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/virtual-network.mdx b/src/content/docs/azure/services/virtual-network.mdx index 141548d6..25ac36b6 100644 --- a/src/content/docs/azure/services/virtual-network.mdx +++ b/src/content/docs/azure/services/virtual-network.mdx @@ -17,12 +17,12 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Virtual Network and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Virtual Network and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. @@ -30,7 +30,7 @@ This command points the `az` CLI away from the public Azure management REST API To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/web-app.mdx b/src/content/docs/azure/services/web-app.mdx index efae0ff3..9cee9b07 100644 --- a/src/content/docs/azure/services/web-app.mdx +++ b/src/content/docs/azure/services/web-app.mdx @@ -15,19 +15,19 @@ The supported APIs are available on our [API Coverage section](#api-coverage), w ## Getting started -This guide is designed for users new to Web App and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script. +This guide is designed for users new to Web App and assumes basic knowledge of the Azure CLI and our `lstk az` proxy. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/web-test.mdx b/src/content/docs/azure/services/web-test.mdx index cd63b6fa..8c2298b7 100644 --- a/src/content/docs/azure/services/web-test.mdx +++ b/src/content/docs/azure/services/web-test.mdx @@ -22,14 +22,14 @@ This guide walks you through creating a web test linked to an Application Insigh Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. diff --git a/src/content/docs/azure/services/workbook.mdx b/src/content/docs/azure/services/workbook.mdx index 6457c29b..2d53fae1 100644 --- a/src/content/docs/azure/services/workbook.mdx +++ b/src/content/docs/azure/services/workbook.mdx @@ -22,14 +22,14 @@ This guide walks you through creating a workbook and a workbook template. Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running: ```bash -azlocal start-interception +lstk az start-interception ``` This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. To revert this configuration, run: ```bash -azlocal stop-interception +lstk az stop-interception ``` This reconfigures the `az` CLI to send commands to the official Azure management REST API. From 42436ffadb8235cf73c65f3eea3b08f857f13025 Mon Sep 17 00:00:00 2001 From: Quetzalli Date: Thu, 23 Jul 2026 14:17:56 +0200 Subject: [PATCH 2/3] DOC-361: Address review feedback on lstk az interception flow 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. --- src/content/docs/azure/integrations/az.md | 38 ++++++++++++++++--- .../docs/azure/services/blob-storage.mdx | 13 ------- .../docs/azure/services/queue-storage.mdx | 5 --- 3 files changed, 32 insertions(+), 24 deletions(-) diff --git a/src/content/docs/azure/integrations/az.md b/src/content/docs/azure/integrations/az.md index 9ab1418c..872d01d3 100644 --- a/src/content/docs/azure/integrations/az.md +++ b/src/content/docs/azure/integrations/az.md @@ -18,31 +18,57 @@ We will demonstrate how to create, show and delete an Azure resource group. ### Prerequisites -This guide uses [`lstk`](/aws/developer-tools/running-localstack/lstk/), which proxies your host `az` CLI against the Azure emulator using an isolated configuration directory, so your global `~/.azure` setup is left untouched. +This guide uses [`lstk`](/aws/developer-tools/running-localstack/lstk/) to point the `az` CLI at the Azure emulator. -Run the following command once to prepare the integration: +To make sure the `az` tool sends requests to the Azure Emulator REST API, run the following command: ``` -$ lstk setup azure +$ lstk az start-interception ``` ### Create and manage the Resource Group -Run the following command to create a resource group in the Emulator, prefixing the same `az` command you would normally run with `lstk az`: +Run the following command to create a resource group in the Emulator: ``` -$ lstk az group create --name MyResourceGroup --location westeurope +$ az group create --name MyResourceGroup --location westeurope ``` To check the resource group details, run the following command: ``` -$ lstk az group show --name MyResourceGroup +$ az group show --name MyResourceGroup ``` To delete the resource group, run the following command: ``` +$ az group delete --name MyResourceGroup --yes +``` + +### Teardown + +When you're done using the Azure Emulator, you can run the following command: + +``` +$ lstk az stop-interception +``` + +The `az` CLI tool will now communicate with the Azure REST API on future invocations. + +### Alternative: prefixed commands + +Instead of interception, you can prefix each `az` command with `lstk az` individually, without changing your global `~/.azure` configuration. Run this once to prepare the integration: + +``` +$ lstk setup azure +``` + +Then prefix every command: + +``` +$ lstk az group create --name MyResourceGroup --location westeurope +$ lstk az group show --name MyResourceGroup $ lstk az group delete --name MyResourceGroup --yes ``` diff --git a/src/content/docs/azure/services/blob-storage.mdx b/src/content/docs/azure/services/blob-storage.mdx index e70a956d..8bb50058 100644 --- a/src/content/docs/azure/services/blob-storage.mdx +++ b/src/content/docs/azure/services/blob-storage.mdx @@ -23,19 +23,6 @@ Launch LocalStack using your preferred method. For more information, see [Introd lstk az start-interception ``` -:::note -As an alternative to using the `lstk az` proxy, users can run: - -`lstk az start-interception` - -This command points the `az` CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator REST API. -To revert this configuration, run: - -`lstk az stop-interception` - -This reconfigures the `az` CLI to send commands to the official Azure management REST API -::: - ### Create a resource group Create a resource group to contain your storage resources: diff --git a/src/content/docs/azure/services/queue-storage.mdx b/src/content/docs/azure/services/queue-storage.mdx index 146c6f27..1c6dbfb1 100644 --- a/src/content/docs/azure/services/queue-storage.mdx +++ b/src/content/docs/azure/services/queue-storage.mdx @@ -25,11 +25,6 @@ Launch LocalStack using your preferred method. For more information, see [Introd lstk az start-interception ``` -:::note -`lstk az start-interception` points the Azure CLI away from the public Azure management REST API and toward the LocalStack for Azure emulator API. -To revert this configuration, run `lstk az stop-interception` so the CLI targets the official Azure management REST API again. -::: - ### Create a resource group Create a resource group to contain your storage resources: From a1a5be3d06d749397b5334f98f5951a3cf1a8997 Mon Sep 17 00:00:00 2001 From: Brian Rinaldi Date: Tue, 28 Jul 2026 16:56:31 -0400 Subject: [PATCH 3/3] Update src/content/docs/azure/integrations/az.md --- src/content/docs/azure/integrations/az.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/azure/integrations/az.md b/src/content/docs/azure/integrations/az.md index 872d01d3..852f2910 100644 --- a/src/content/docs/azure/integrations/az.md +++ b/src/content/docs/azure/integrations/az.md @@ -54,7 +54,7 @@ When you're done using the Azure Emulator, you can run the following command: $ lstk az stop-interception ``` -The `az` CLI tool will now communicate with the Azure REST API on future invocations. +The `az` CLI tool will now communicate with the Azure cloud on future invocations. ### Alternative: prefixed commands