azure-deploy-cli 0.1.12__tar.gz → 1.0.1__tar.gz

{azure_deploy_cli-0.1.12 → azure_deploy_cli-1.0.1}/.github/workflows/1-3-release.yaml

@@ -61,16 +61,15 @@ jobs:
         uses: actions/setup-python@v6
         with:
           python-version: '3.11'
-          cache: 'pip'
 
-      - name: Install build dependencies
-        run: |
-          python -m pip install --upgrade pip
-          pip install build
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+        with:
+          enable-cache: true
 
       - name: Build package
         run: |
-          python -m build
+          uv build
 
       - name: Publish package distributions to PyPI
         uses: pypa/gh-action-pypi-publish@release/v1

{azure_deploy_cli-0.1.12 → azure_deploy_cli-1.0.1}/.github/workflows/2-build.yaml

@@ -15,10 +15,14 @@ jobs:
         uses: actions/setup-python@v6
         with:
           python-version: '3.11'
-          cache: 'pip'
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+        with:
+          enable-cache: true
 
       - name: Install dependencies
-        run: make install-dev
+        run: source setup.sh --install
 
       - name: Lint
         run: make lint

{azure_deploy_cli-0.1.12 → azure_deploy_cli-1.0.1}/.pre-commit-config.yaml

@@ -22,7 +22,7 @@ repos:
     rev: v1.11.2
     hooks:
       - id: mypy
-        additional_dependencies: []
+        additional_dependencies: [types-PyYAML]
         args: [--config-file=pyproject.toml]
         exclude: ^tests/
 

{azure_deploy_cli-0.1.12 → azure_deploy_cli-1.0.1}/CHANGELOG.md

@@ -1,3 +1,13 @@
+## [1.0.1] - 2026-01-18
+
+### ⚙️ Miscellaneous Tasks
+
+- Use uv (#29)
+## [1.0.0] - 2026-01-09
+
+### 🚀 Features
+
+- [**breaking**] Add new required YAML-based multi-container configuration for Azure Container Apps (#27)
 ## [0.1.12] - 2026-01-06
 
 ### 🐛 Bug Fixes

azure_deploy_cli-1.0.1/CONTRIBUTING.md

@@ -0,0 +1,163 @@
+# Contributing to Azure Deploy CLI
+
+## Prerequisites
+
+- Python 3.11 or higher
+- `uv` (Python package manager) - [Install uv](https://docs.astral.sh/uv/getting-started/installation/)
+
+## Development Setup
+
+**Create and activate a virtual environment:**
+
+```bash
+source setup.sh -i
+```
+
+This will:
+- Create a `.venv` virtual environment using `uv` with Python 3.11
+- Install all dependencies (base + dev)
+- Print activation instructions
+
+**Manual setup without setup.sh:**
+
+```bash
+uv venv -p 3.11 .venv
+source .venv/bin/activate
+uv sync --all-extras
+```
+
+## Managing Dependencies
+
+This project uses `uv` for dependency management with pinned versions in `pyproject.toml` for reproducibility.
+
+### Tips for pip users transitioning to uv
+
+| Task | pip | uv |
+|------|-----|-----|
+| **Install dependencies** | `pip install -r requirements.txt` | `uv sync` |
+| **Add a package** | `pip install package-name` | `uv pip install package-name` |
+| **Create venv** | `python -m venv venv` | `uv venv` |
+| **Freeze dependencies** | `pip freeze > requirements.txt` | `uv pip freeze` or `uv.lock` |
+| **Update lock file** | Manual via pip freeze | `uv sync` (automatic) |
+| **Specify Python version** | N/A | `uv venv -p 3.11` |
+| **Install dev deps** | `pip install -r requirements-dev.txt` | `uv sync --all-extras` |
+
+### Adding New Dependencies
+
+```bash
+# Add to production dependencies
+uv pip install package-name
+
+# Add to dev dependencies
+uv pip install --group dev package-name
+
+# Update lock file and sync
+uv sync
+```
+
+Then update `pyproject.toml` to include the new dependency with its pinned version (run `uv pip freeze` to get the exact version).
+
+## Build and Test Commands
+
+```bash
+make install-dev    # Install with dev tools
+make build          # Run lint + type-check + test
+make lint           # Code linting with ruff
+make format         # Auto-format code
+make type-check     # Type checking with mypy
+make test           # Run tests with pytest
+make test-cov       # Run tests with coverage report
+make clean          # Remove build artifacts
+```
+
+## Version Management and Changelog
+
+This project uses a dual-tool approach for versioning and releases:
+
+- **[setuptools-scm](https://setuptools-scm.readthedocs.io/)** - Automatic versioning based on git tags (dynamic at build time)
+- **[commitizen](https://commitizen-tools.github.io/commitizen/)** - Version bumping and tagging with semantic versioning
+- **[git-cliff](https://git-cliff.org/)** - Automatic changelog generation from conventional commits
+
+### Release Workflow
+
+1. **Create a commit** using [Conventional Commits](https://www.conventionalcommits.org/) format (e.g., `feat: add feature`, `fix: resolve bug`)
+   - Optionally use `make commit` for interactive conventional commit creation with `commitizen`
+2. **git-cliff** automatically generates changelog from commits since last tag
+3. **commitizen** bumps version and creates git tag
+4. **New version is committed** alongside updated CHANGELOG
+5. **Git tag** triggers PyPI publishing and GitHub Release
+
+**No manual version or changelog updates are needed** — all are generated automatically.
+
+### Commit Convention
+
+Use [Conventional Commits](https://www.conventionalcommits.org/) format:
+
+```
+<type>(<scope>): <subject>
+
+<body>
+
+<footer>
+```
+
+**Type:** `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`
+
+**Examples:**
+- `feat: add support for cosmos-db roles`
+- `fix: correct azure identity authentication`
+- `docs: update ACA deployment example`
+- `chore: upgrade dependencies`
+
+### Making a Release
+
+```bash
+# Ensure all changes are committed
+git status
+
+# Create a conventional commit
+make commit
+
+# Commitizen will:
+# - Bump version (major/minor/patch)
+# - Create git tag
+# - Update CHANGELOG
+# - Commit changes
+
+# Push changes and tag
+git push origin main --tags
+```
+
+The CI/CD pipeline will automatically:
+- Build the package
+- Run tests
+- Publish to PyPI
+- Create a GitHub Release
+
+## Pre-commit Hooks
+
+Pre-commit hooks are automatically installed during development setup and enforce code quality standards:
+
+```bash
+# Manually run pre-commit on all files
+pre-commit run --all-files
+
+# Run specific hook
+pre-commit run ruff --all-files
+```
+
+## Scripting and Output Handling
+
+This CLI is designed for both interactive use and automated scripting. To support this, it separates output streams:
+
+- **`stderr`**: All human-readable logs, progress indicators, and error messages
+- **`stdout`**: All machine-readable output (e.g., revision names, IDs)
+
+When developing features that produce output:
+- Use `sys.stderr` for logging and user-facing messages
+- Use `sys.stdout` for machine-readable output only
+- This allows scripts to cleanly capture output while still seeing logs
+
+## License
+
+Mozilla Public License 2.0 - See LICENSE file for details

{azure_deploy_cli-0.1.12 → azure_deploy_cli-1.0.1}/Makefile

@@ -18,34 +18,33 @@ help:
 	@echo "  build            Run linting, type checking, and tests"
 
 setup-hooks:
-	pre-commit install
-	pre-commit install --hook-type commit-msg
+	uv run pre-commit install
+	uv run pre-commit install --hook-type commit-msg
 
 install:
-	pip install .
-	$(MAKE) setup-hooks
+	uv sync
 
 install-dev:
-	pip install -e ".[dev]"
+	uv sync --all-extras
 	$(MAKE) setup-hooks
 
 commit:
-	cz commit
+	uv run cz commit
 
 lint:
-	ruff check src/ tests/ 2>/dev/null || echo "No issues found"
+	uv run ruff check src/ tests/ 2>/dev/null || echo "No issues found"
 
 format:
-	ruff format src/ tests/
+	uv run ruff format src/ tests/
 
 type-check:
-	mypy src/azure_deploy_cli
+	uv run mypy src/azure_deploy_cli
 
 test:
-	pytest tests/ -v
+	uv run pytest tests/ -v
 
 test-cov:
-	pytest tests/ -v --cov=src/azure_deploy_cli --cov-report=html --cov-report=term-missing
+	uv run pytest tests/ -v --cov=src/azure_deploy_cli --cov-report=html --cov-report=term-missing
 
 clean:
 	find . -type d -name "__pycache__" -exec rm -rf {} + 2>/dev/null || true

{azure_deploy_cli-0.1.12 → azure_deploy_cli-1.0.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: azure-deploy-cli
-Version: 0.1.12
+Version: 1.0.1
 Summary: Python CLI for Azure deployment automation - identity, roles, and container apps management
 Author-email: decewei <celinew1221@gmail.com>
 License: Mozilla Public License Version 2.0
@@ -386,84 +386,68 @@ Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: Mozilla Public License 2.0 (MPL 2.0)
 Classifier: Natural Language :: English
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
-Requires-Python: >=3.10
+Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: azure-identity>=1.14.0
-Requires-Dist: azure-mgmt-appcontainers
-Requires-Dist: azure-mgmt-authorization
-Requires-Dist: azure-mgmt-keyvault
-Requires-Dist: azure-mgmt-msi
-Requires-Dist: python-dotenv>=1.0.0
-Requires-Dist: pydantic>=2.0.0
+Requires-Dist: azure-identity==1.25.1
+Requires-Dist: azure-mgmt-appcontainers==4.0.0
+Requires-Dist: azure-mgmt-authorization==4.0.0
+Requires-Dist: azure-mgmt-keyvault==13.0.0
+Requires-Dist: azure-mgmt-msi==7.1.0
+Requires-Dist: python-dotenv==1.2.1
+Requires-Dist: pydantic==2.12.5
+Requires-Dist: PyYAML==6.0.3
 Provides-Extra: dev
-Requires-Dist: ruff>=0.1.0; extra == "dev"
-Requires-Dist: mypy>=1.7.0; extra == "dev"
-Requires-Dist: pytest>=7.0; extra == "dev"
-Requires-Dist: pytest-asyncio>=0.21.0; extra == "dev"
-Requires-Dist: coverage>=7.3.0; extra == "dev"
-Requires-Dist: pytest-cov>=4.0.0; extra == "dev"
-Requires-Dist: commitizen>=3.0.0; extra == "dev"
-Requires-Dist: pre-commit>=3.0.0; extra == "dev"
-Requires-Dist: types-setuptools; extra == "dev"
+Requires-Dist: ruff==0.14.10; extra == "dev"
+Requires-Dist: mypy==1.19.1; extra == "dev"
+Requires-Dist: pytest==9.0.2; extra == "dev"
+Requires-Dist: pytest-asyncio==1.3.0; extra == "dev"
+Requires-Dist: coverage==7.13.1; extra == "dev"
+Requires-Dist: pytest-cov==7.0.0; extra == "dev"
+Requires-Dist: commitizen==4.11.0; extra == "dev"
+Requires-Dist: pre-commit==4.1.0; extra == "dev"
+Requires-Dist: types-setuptools==80.9.0.20251223; extra == "dev"
+Requires-Dist: types-PyYAML==6.0.12.20250915; extra == "dev"
 Dynamic: license-file
 
 # Azure Deploy CLI
 
 Python CLI for Azure deployment automation - manage identities, roles, and Container Apps deployments.
 
-## Version Management and Changelog
-
-This project uses a dual-tool approach:
-
-- **[setuptools-scm](https://setuptools-scm.readthedocs.io/)** - Automatic versioning based on git tags (dynamic at build time)
-- **[commitizen](https://commitizen-tools.github.io/commitizen/)** - Version bumping and tagging with semantic versioning
-- **[git-cliff](https://git-cliff.org/)** - Automatic changelog generation from conventional commits
-
-**Release workflow:**
-1. git-cliff generates changelog from commits since last tag
-2. commitizen bumps version and creates git tag
-3. New version is committed alongside updated changelog
-4. Tag triggers PyPI publishing and GitHub Release
-
-No manual version or changelog updates are needed.
-
 ## Quick Start
 
 **Install for development:**
 
 ```bash
 cd /path/to/azure-deploy-cli
-pip install -e ".[dev]"
+source setup.sh -i
 azd --help
 ```
 
 **Use in another project:**
 
 ```bash
-pip install -e /path/to/scripts
+pip install azure-deploy-cli
 ```
 
 ## Installation
 
-| Method | Command |
-|--------|----------|
-| Local development | `pip install -e ".[dev]"` |
-| Local changes | `pip install -e /path/to/azure-deploy-cli` |
-| From PyPI | `pip install azure-deploy-cli` |
+| Method              | Command                       |
+| ------------------- | ----------------------------- |
+| Local development   | `source setup.sh -i`          |
+| From PyPI           | `pip install azure-deploy-cli`|
 
 ## CLI Commands
 
 ### Azure Container Apps (ACA) Deployment
 
-The ACA deployment process is split into two stages for better control:
+The ACA deployment process uses YAML configuration for containers and is split into two stages for better control:
 
 #### Stage 1: Deploy Revision
 
-Deploy a new container revision without affecting traffic:
+Deploy a new container revision from YAML configuration without affecting traffic:
 
 ```bash
 azd azaca deploy \
@@ -474,25 +458,76 @@ azd azaca deploy \
   --user-assigned-identity-name my-identity \
   --container-app my-app \
   --registry-server myregistry.azurecr.io \
-  --image-name my-image \
   --stage prod \
-  --target-port 8000 \
-  --cpu 0.5 \
-  --memory 1.0 \
+  --target-port 8080 \
   --min-replicas 1 \
   --max-replicas 10 \
   --keyvault-name my-keyvault \
-  --dockerfile ./Dockerfile \
-  --env-vars ENV_VAR1 ENV_VAR2 \
+  --container-config ./container-config.yaml \
   --env-var-secrets SECRET1 SECRET2
 ```
 
 This command:
 
+- Loads container configurations from YAML file
+- Builds/pushes container images for all containers
 - Creates or updates a new revision with 0% traffic
+- Supports multiple containers with independent configurations
 - Verifies the revision is healthy and active
 - Outputs the revision name for use in traffic management
 
+**Container Configuration YAML:**
+
+The `--container-config` file specifies container settings including images, resources, environment variables, and health probes:
+
+```yaml
+containers:
+  - name: my-app
+    image_name: my-image
+    cpu: 0.5
+    memory: "1.0Gi"
+    env_vars:
+      - ENV_VAR1
+      - ENV_VAR2
+    # relative to the directory which command will run fromm
+    dockerfile: ./Dockerfile
+    probes:
+      - type: Liveness
+        http_get:
+          path: /health
+          port: 8080
+        initial_delay_seconds: 10
+        period_seconds: 30
+      - type: Readiness
+        http_get:
+          path: /ready
+          port: 8080
+        initial_delay_seconds: 5
+        period_seconds: 10
+
+  - name: sidecar
+    image_name: sidecar-image
+    cpu: 0.25
+    memory: "0.5Gi"
+    env_vars:
+      - SIDECAR_CONFIG
+    existing_image_tag: v1.0.0  # Optional: retag from existing image
+```
+
+**Configuration Fields:**
+
+- `containers` (required): List of container configurations
+  - `name`: Container name (required)
+  - `image_name`: Image name without registry/tag (required)
+  - `cpu`: CPU allocation (required, e.g., 0.5)
+  - `memory`: Memory allocation (required, e.g., "1.0Gi")
+  - `env_vars`: List of environment variable names to load (optional)
+  - `dockerfile`: Path to Dockerfile for building (required if existing_image_tag not provided)
+  - `existing_image_tag`: Tag to retag from instead of building (required if dockerfile not provided)
+  - `probes`: List of health probes (optional)
+
+**Note:** Ingress configuration (target port) and scaling parameters (min/max replicas) are specified via CLI arguments, not in the YAML file.
+
 #### Stage 2: Update Traffic Weights
 
 Update traffic distribution and deactivate old revisions:
@@ -603,20 +638,6 @@ azd create-and-assign \
   --print
 ```
 
-## Development
-
-```bash
-make install-dev    # Install with dev tools
-make build          # Run lint + type-check + test
-make lint           # Code linting with ruff
-make format         # Auto-format code
-make type-check     # Type checking with mypy
-make test           # Run tests with pytest
-make clean          # Remove build artifacts
-```
-
-Commit using [Conventional Commits](https://www.conventionalcommits.org/) format (e.g., `feat: add feature`, `fix: resolve bug`)
-
 ## Scripting and Output Handling
 
 This CLI is designed for both interactive use and automated scripting. To support this, it follows the standard practice of separating output streams:

{azure_deploy_cli-0.1.12 → azure_deploy_cli-1.0.1}/README.md

@@ -2,55 +2,38 @@
 
 Python CLI for Azure deployment automation - manage identities, roles, and Container Apps deployments.
 
-## Version Management and Changelog
-
-This project uses a dual-tool approach:
-
-- **[setuptools-scm](https://setuptools-scm.readthedocs.io/)** - Automatic versioning based on git tags (dynamic at build time)
-- **[commitizen](https://commitizen-tools.github.io/commitizen/)** - Version bumping and tagging with semantic versioning
-- **[git-cliff](https://git-cliff.org/)** - Automatic changelog generation from conventional commits
-
-**Release workflow:**
-1. git-cliff generates changelog from commits since last tag
-2. commitizen bumps version and creates git tag
-3. New version is committed alongside updated changelog
-4. Tag triggers PyPI publishing and GitHub Release
-
-No manual version or changelog updates are needed.
-
 ## Quick Start
 
 **Install for development:**
 
 ```bash
 cd /path/to/azure-deploy-cli
-pip install -e ".[dev]"
+source setup.sh -i
 azd --help
 ```
 
 **Use in another project:**
 
 ```bash
-pip install -e /path/to/scripts
+pip install azure-deploy-cli
 ```
 
 ## Installation
 
-| Method | Command |
-|--------|----------|
-| Local development | `pip install -e ".[dev]"` |
-| Local changes | `pip install -e /path/to/azure-deploy-cli` |
-| From PyPI | `pip install azure-deploy-cli` |
+| Method              | Command                       |
+| ------------------- | ----------------------------- |
+| Local development   | `source setup.sh -i`          |
+| From PyPI           | `pip install azure-deploy-cli`|
 
 ## CLI Commands
 
 ### Azure Container Apps (ACA) Deployment
 
-The ACA deployment process is split into two stages for better control:
+The ACA deployment process uses YAML configuration for containers and is split into two stages for better control:
 
 #### Stage 1: Deploy Revision
 
-Deploy a new container revision without affecting traffic:
+Deploy a new container revision from YAML configuration without affecting traffic:
 
 ```bash
 azd azaca deploy \
@@ -61,25 +44,76 @@ azd azaca deploy \
   --user-assigned-identity-name my-identity \
   --container-app my-app \
   --registry-server myregistry.azurecr.io \
-  --image-name my-image \
   --stage prod \
-  --target-port 8000 \
-  --cpu 0.5 \
-  --memory 1.0 \
+  --target-port 8080 \
   --min-replicas 1 \
   --max-replicas 10 \
   --keyvault-name my-keyvault \
-  --dockerfile ./Dockerfile \
-  --env-vars ENV_VAR1 ENV_VAR2 \
+  --container-config ./container-config.yaml \
   --env-var-secrets SECRET1 SECRET2
 ```
 
 This command:
 
+- Loads container configurations from YAML file
+- Builds/pushes container images for all containers
 - Creates or updates a new revision with 0% traffic
+- Supports multiple containers with independent configurations
 - Verifies the revision is healthy and active
 - Outputs the revision name for use in traffic management
 
+**Container Configuration YAML:**
+
+The `--container-config` file specifies container settings including images, resources, environment variables, and health probes:
+
+```yaml
+containers:
+  - name: my-app
+    image_name: my-image
+    cpu: 0.5
+    memory: "1.0Gi"
+    env_vars:
+      - ENV_VAR1
+      - ENV_VAR2
+    # relative to the directory which command will run fromm
+    dockerfile: ./Dockerfile
+    probes:
+      - type: Liveness
+        http_get:
+          path: /health
+          port: 8080
+        initial_delay_seconds: 10
+        period_seconds: 30
+      - type: Readiness
+        http_get:
+          path: /ready
+          port: 8080
+        initial_delay_seconds: 5
+        period_seconds: 10
+
+  - name: sidecar
+    image_name: sidecar-image
+    cpu: 0.25
+    memory: "0.5Gi"
+    env_vars:
+      - SIDECAR_CONFIG
+    existing_image_tag: v1.0.0  # Optional: retag from existing image
+```
+
+**Configuration Fields:**
+
+- `containers` (required): List of container configurations
+  - `name`: Container name (required)
+  - `image_name`: Image name without registry/tag (required)
+  - `cpu`: CPU allocation (required, e.g., 0.5)
+  - `memory`: Memory allocation (required, e.g., "1.0Gi")
+  - `env_vars`: List of environment variable names to load (optional)
+  - `dockerfile`: Path to Dockerfile for building (required if existing_image_tag not provided)
+  - `existing_image_tag`: Tag to retag from instead of building (required if dockerfile not provided)
+  - `probes`: List of health probes (optional)
+
+**Note:** Ingress configuration (target port) and scaling parameters (min/max replicas) are specified via CLI arguments, not in the YAML file.
+
 #### Stage 2: Update Traffic Weights
 
 Update traffic distribution and deactivate old revisions:
@@ -190,20 +224,6 @@ azd create-and-assign \
   --print
 ```
 
-## Development
-
-```bash
-make install-dev    # Install with dev tools
-make build          # Run lint + type-check + test
-make lint           # Code linting with ruff
-make format         # Auto-format code
-make type-check     # Type checking with mypy
-make test           # Run tests with pytest
-make clean          # Remove build artifacts
-```
-
-Commit using [Conventional Commits](https://www.conventionalcommits.org/) format (e.g., `feat: add feature`, `fix: resolve bug`)
-
 ## Scripting and Output Handling
 
 This CLI is designed for both interactive use and automated scripting. To support this, it follows the standard practice of separating output streams: