azure-cosmos-db-py

Topics in the source

• Cosmos DB Service Implementation
• Installation
• Environment Variables
• Authentication & Lifecycle
• Architecture Overview
• Quick Start
• 1. Client Module Setup
• 2. Pydantic Model Hierarchy

Build production-grade Azure Cosmos DB NoSQL services following clean code, security best practices, and TDD principles. 🔑 Two rules apply to every code sample below: 1. Prefer DefaultAzureCredential. It works locally (Azure CLI / VS Code / Developer CLI) and in Azure (managed identity, workload identity) with no code change. Avoid connection strings, account/API keys — they bypass Entra audit and rotation. - Local dev: DefaultAzureCredential works as-is. - Production: set AZURETOKENCREDENTIALS=prod (or AZURETOKENCREDENTIALS= ) to constrain the credential chain to production-safe credentials. 2. Wrap every client in a context manager so HTTP transports, sockets, and token caches are released deterministically: - Sync: with (...) as client: - Async: async with (...) as client: and async with DefaultAzureCredential() as credential: (from azure.identity.aio) Snippets may abbreviate this setup, but production code should always follow both rules. DefaultAzureCredential (preferred): Emulator (local development): Create a singleton Cosmos client with dual authentication: Full implementation: See references/client-setup.md Use five-tier model pattern for clean separation: Full patterns:

This is an excerpt. Refer to the complete source and its current requirements.