topaz-sdk
Python SDK for Topaz — the single-binary Azure emulator.
What is Topaz?
Topaz is a single-binary local Azure emulator. Instead of running Azurite for Storage, a separate emulator for Service Bus, and another for Key Vault — you run one tool that covers the control and data planes of many Azure services, emulates ARM deployments, and implements Azure RBAC, all with no Azure subscription required.
Installation
pip install topaz-sdk
Requires Python 3.10 or later.
Quick start
from topaz_sdk import AzureLocalCredential, TopazArmClient, GLOBAL_ADMIN_ID
# Authenticate as the built-in admin user
credential = AzureLocalCredential(GLOBAL_ADMIN_ID)
client = TopazArmClient(credential)
# Create a subscription and resource group
client.create_subscription("my-subscription", "00000000-0000-0000-0000-000000000001")
client.create_resource_group(
"00000000-0000-0000-0000-000000000001",
"my-resource-group",
"westeurope",
)
Using standard Azure SDK clients
topaz-sdk provides credentials and helpers that work directly with the standard azure-mgmt-* packages:
from azure.mgmt.keyvault import KeyVaultManagementClient
from topaz_sdk import AzureLocalCredential, GLOBAL_ADMIN_ID, DEFAULT_RESOURCE_MANAGER_PORT
credential = AzureLocalCredential(GLOBAL_ADMIN_ID)
client = KeyVaultManagementClient(
credential=credential,
subscription_id="00000000-0000-0000-0000-000000000001",
base_url=f"https://topaz.local.dev:{DEFAULT_RESOURCE_MANAGER_PORT}",
credential_scopes=["https://topaz.local.dev/.default"],
)
Point any azure-mgmt-* client at Topaz by overriding base_url and credential_scopes. No application code changes are required.
Provided classes
| Symbol | Description |
|---|---|
AzureLocalCredential |
TokenCredential implementation for Topaz's built-in identity endpoint |
TopazArmClient |
Thin HTTP client for management-plane operations not covered by azure-mgmt-resource (subscription lifecycle, resource groups, management groups, role assignments) |
GLOBAL_ADMIN_ID |
Constant for the built-in admin user ID (00000000-0000-0000-0000-000000000000) |
DEFAULT_RESOURCE_MANAGER_PORT |
Default ARM port (8899) |
Requirements
The SDK expects a running Topaz host. See the Topaz quickstart for installation instructions.
SSL verification uses the REQUESTS_CA_BUNDLE environment variable. When running inside the Topaz test fixture container this is set automatically.
Links
- Docs: topaz.thecloudtheory.com
- Source: github.com/TheCloudTheory/Topaz
- Issues: github.com/TheCloudTheory/Topaz/issues
- Discord: discord.gg/eGTkS76w
Metadata
Release files for topaz-sdk 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| topaz_sdk-0.1.2.tar.gz | 10.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| topaz_sdk-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.2 kB
Release files / topaz_sdk-0.1.2.tar.gz
| Download URL | topaz_sdk-0.1.2.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ab8d28855a0bf53a3aeed25249d464efe391315ad392ce50c4f4ff502ba53a9
|
|
BLAKE2b-256 checksum How to use checksums |
3f1497a87a3deac039cd43fc49e0926073185879fad85fb4c9d4f59d1b8a833a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 23, 2026.
Transparency logRelease files / topaz_sdk-0.1.2-py3-none-any.whl
| Download URL | topaz_sdk-0.1.2-py3-none-any.whl |
|---|---|
| Size | 11.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0b50307a10df20cb2c4f6b2ad85aaebadbeb0cdf2ebb620b43ca0fdd52a30a2f
|
|
BLAKE2b-256 checksum How to use checksums |
c775dbea95bf6b681e3153a060e1cd9987958ff75c2908ec227aee54a2bfe234
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 23, 2026.
Transparency log