prefect-deployments-toolkit 0.0.1__tar.gz

prefect_deployments_toolkit-0.0.1/.github/workflows/cd.yml

@@ -0,0 +1,68 @@
+name: Release
+
+on:
+  workflow_dispatch:
+    inputs:
+      version:
+        description: "The release version."
+        required: true
+        default: "v0.x.x"
+
+jobs:
+  build-distribution:
+    name: Build distribution 📦
+    timeout-minutes: 5
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - name: Set up Python
+        uses: actions/setup-python@v6
+        with:
+          python-version: "3.13"
+      - name: Install pypa/build
+        run: python3 -m pip install build --user
+      - name: Build a binary wheel and a source tarball
+        run: python3 -m build
+      - name: Store the distribution packages
+        uses: actions/upload-artifact@v7
+        with:
+          name: python-package-distributions
+          path: dist/
+
+  publish-to-pypi:
+    name: Publish to PyPI 🚀
+    timeout-minutes: 5
+    needs:
+      - build-distribution
+    runs-on: ubuntu-latest
+    environment:
+      name: release
+      url: https://pypi.org/p/prefect-deployments-toolkit
+    permissions:
+      id-token: write # IMPORTANT: this permission is mandatory for trusted publishing
+    steps:
+      - name: Download all the dists
+        uses: actions/download-artifact@v8
+        with:
+          name: python-package-distributions
+          path: dist/
+      - name: Publish package distributions to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          verbose: true
+
+  create_github_release:
+    name: Create a GitHub release 🔖
+    timeout-minutes: 5
+    needs:
+      - publish-to-pypi
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v6
+      - name: Create a release
+        uses: ncipollo/release-action@339a81892b84b4eeb0f6e744e4574d79d0d9b8dd #v1.21.0
+        with:
+          generateReleaseNotes: true
+          tag: ${{ github.event.inputs.version }}

prefect_deployments_toolkit-0.0.1/.github/workflows/detect-and-tag-new-version.yml

@@ -0,0 +1,56 @@
+# Detect if package version has been bumped & if so, trigger a release.
+
+# Take the version from pyproject.toml and check if a git tag for this version exists.
+# If not, trigger the release workflow (cd.yml) by pushing a new tag to the repository.
+
+name: Detect and tag new version
+
+on:
+  push:
+    branches:
+      - "main"
+  workflow_dispatch:
+
+jobs:
+  check-version-and-push-tag:
+    name: Detect and create a tag for new version
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+
+      - name: Get package version from pyproject.toml
+        id: get-version
+        run: |
+          VERSION=$(uv version | grep -oP '\d+\.\d+\.\d+.*')
+          echo "version=$VERSION" >> $GITHUB_OUTPUT
+
+      - name: Check if a tag for this version already exists in the repo
+        uses: mukunku/tag-exists-action@5c39604fe8aef7e65acb6fbcf96ec580f7680313 #v1.7.0
+        id: check-tag
+        with:
+          tag: v${{ steps.get-version.outputs.version }}
+
+      - uses: fregante/setup-git-user@024bc0b8e177d7e77203b48dab6fb45666854b35 # v2.0.2
+        if: steps.check-tag.outputs.exists != 'true'
+
+      - name: Publish the new tag
+        # Trigger the cd.yml workflow if a new tag is detected.
+        id: publish-tag
+        if: steps.check-tag.outputs.exists != 'true'
+        run: |
+          git tag -a v${{ steps.get-version.outputs.version }} -m "Release v${{ steps.get-version.outputs.version }}"
+          git push origin v${{ steps.get-version.outputs.version }}
+
+      - name: Run the release workflow
+        if: steps.check-tag.outputs.exists != 'true'
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: gh workflow run cd.yml -f version=v${{ steps.get-version.outputs.version }} --ref main

prefect_deployments_toolkit-0.0.1/CHANGELOG.md

@@ -0,0 +1,23 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.0.1] - 2026-07-03
+
+### Added
+
+- Initial release of the toolkit.
+- `get_modified_deployments` module to detect added, modified, and removed Prefect deployments between two git references.
+- Unified handling of `push`, `pull_request`, and `pull_request_target` CI event types for change detection.
+- `apply_deployments` module (via `__main__`) to create, update, or delete Prefect deployments concurrently.
+- Dual backend support: `cli` (wraps `prefect deploy`) and `rest` (direct Prefect Cloud REST API calls).
+- Dev environment overrides: deployment name prefixing, work pool substitution, and schedule pausing.
+- Duplicate deployment name detection with optional automatic cleanup (`--enforce-unique-deployment-names`).
+- Thread-safe, non-interleaved log buffering for concurrent deployment runs.
+- YAML schedule validation (rejects singular `schedule` key, empty `schedules`, and entries missing `cron`).
+
+[0.0.1]: https://github.com/yourusername/prefect-deployments-toolkit/releases/tag/v0.0.1
+

prefect_deployments_toolkit-0.0.1/LICENSE

@@ -0,0 +1,132 @@
+PolyForm Noncommercial License 1.0.0
+
+<https://polyformproject.org/licenses/noncommercial/1.0.0>
+
+Copyright (c) 2026 [Your Name or Organization]
+
+## Acceptance
+
+In order to get any license under these terms, you must agree
+to them as both strict obligations and conditions to all
+your licenses.
+
+## Copyright License
+
+The licensor grants you a copyright license for the software
+to do everything you might do with the software that would
+otherwise infringe the licensor's copyright in it for any
+permitted purpose. However, you may only distribute the
+software according to Distribution License and make changes
+or new works based on the software according to Changes
+and New Works License.
+
+## Distribution License
+
+The licensor grants you an additional copyright license to
+distribute copies of the software. Your license to distribute
+covers distributing the software with changes and new works
+permitted by Changes and New Works License.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of
+the software from you also gets a copy of these terms or the
+URL for them above, as well as copies of any plain-text lines
+beginning with `Required Notice` that the licensor provided
+with the software. For example:
+
+> Required Notice: Copyright Yoyodyne, Inc. (http://example.com)
+
+## Changes and New Works License
+
+The licensor grants you an additional copyright license to
+make changes and new works based on the software for any
+permitted purpose.
+
+## Patent License
+
+The licensor grants you a patent license for the software that
+covers patent claims the licensor can license, or becomes able
+to license, that you would infringe by using the software.
+
+## Noncommercial Purposes
+
+Any noncommercial purpose is a permitted purpose.
+
+## Personal Uses
+
+Personal use for research, experiment, and testing for the
+benefit of public knowledge, personal study, private
+entertainment, hobby projects, amateur pursuits, or religious
+observance, without any anticipated commercial application,
+is use for a permitted purpose.
+
+## Noncommercial Organizations
+
+Use by any charitable organization, educational institution,
+public research organization, public safety or health
+organization, environmental protection organization, or
+government institution is use for a permitted purpose
+regardless of the source of funding or obligations resulting
+from the funding.
+
+## Fair Use
+
+You may have "fair use" rights for the software under the
+law. These terms do not limit them.
+
+## No Other Rights
+
+These terms do not allow you to sublicense or transfer any of
+your licenses to anyone else, or prevent the licensor from
+granting licenses to anyone else. These terms do not imply
+any other licenses.
+
+## Patent Defense
+
+If you make any written claim that the software infringes or
+contributes to infringement of any patent, your patent license
+for the software granted under these terms ends immediately.
+If your company makes such a claim, your patent license ends
+immediately for work on behalf of your company.
+
+## Violations
+
+The first time you are notified in writing that you have
+violated any of these terms, or done anything with the
+software not covered by your licenses, your licenses can
+nonetheless continue if you come into full compliance with
+these terms, and take practical steps to correct past
+violations, within 32 days of receiving notice. Otherwise, all
+your licenses end immediately.
+
+## No Liability
+
+As far as the law allows, the software comes as is, without
+any warranty or condition, and the licensor will not be liable
+to you for any damages arising out of these terms or the use
+or nature of the software, under any kind of legal claim.
+
+## Definitions
+
+The **licensor** is the individual or entity offering these
+terms, and the **software** is the software the licensor makes
+available under these terms.
+
+**You** refers to the individual or entity agreeing to these
+terms.
+
+**Your company** is any legal entity, sole proprietorship, or
+other kind of organization that you work for, plus all
+organizations that have control over, are under the control of,
+or are under common control with that organization. **Control**
+means ownership of substantially all the assets of an entity,
+or the power to direct its management and policies by vote,
+contract, or otherwise. Control can be direct or indirect.
+
+**Your licenses** are all the licenses granted to you for the
+software under these terms.
+
+**Use** means anything you do with the software requiring one
+of your licenses.
+

prefect_deployments_toolkit-0.0.1/PKG-INFO

@@ -0,0 +1,114 @@
+Metadata-Version: 2.4
+Name: prefect-deployments-toolkit
+Version: 0.0.1
+Summary: CLI toolkit for detecting and applying Prefect deployment changes in CI/CD pipelines
+Project-URL: Repository, https://github.com/dyvenia/prefect-deployments-toolkit
+Project-URL: Issues, https://github.com/dyvenia/prefect-deployments-toolkit/issues
+Author-email: k-wolski <kwolski@dyvenia.com>
+License: PolyForm-Noncommercial-1.0.0
+License-File: LICENSE
+Keywords: ci-cd,deployment,gitlab-ci,prefect,workflow-orchestration
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: System :: Systems Administration
+Requires-Python: >=3.10
+Requires-Dist: httpx>=0.27
+Requires-Dist: prefect<4,>=3.0
+Requires-Dist: pyyaml>=6.0
+Description-Content-Type: text/markdown
+
+# Prefect Deployments Toolkit
+
+A lightweight CLI toolkit for managing Prefect deployment lifecycles in CI/CD pipelines. It detects deployments that were added, modified, or removed between two git references, and applies (creates, updates, or deletes) those deployments against Prefect Cloud or a self-hosted Prefect server — via either the Prefect CLI or direct REST API calls.
+
+Built for teams running many Prefect flows out of a monorepo, where each deployment is defined in its own YAML file alongside a shared `prefect_base.yaml`, and CI needs to figure out *which* deployments actually changed before re-registering them.
+
+## Features
+
+- **Change detection** — diff deployments between two git refs (a merge request source vs. target branch, or `HEAD~1` vs. `HEAD` after a merge) and get back exactly which deployments were added, modified, or removed.
+- **Unified push / pull-request logic** — one code path handles both `pull_request` (compare local files against a fetched base branch) and `push`/`pull_request_target` (compare `HEAD~1` against `HEAD`) event styles.
+- **Dual deploy backends** — apply deployments using the `prefect` CLI as a subprocess, or bypass it entirely with direct Prefect Cloud REST API calls for faster, more controllable deploys.
+- **Dev/prod environment overrides** — automatic name prefixing, work pool substitution, and schedule pausing for dev environments.
+- **Concurrent deployment application** — apply multiple deployments in parallel with clean, non-interleaved log output per deployment.
+- **Duplicate deployment name detection** — warns (or optionally cleans up) when the same deployment name resolves to more than one flow.
+
+## Installation
+
+```bash
+pip install prefect-deployments-toolkit
+```
+
+Requires Python >= 3.10.
+
+## Usage
+
+### 1. Detect modified deployments
+
+```bash
+python -m prefect_deployments_toolkit.get_modified_deployments \
+  --modified-by push \
+  --base-ref main \
+  --deployments-dir deployments
+```
+
+Prints a comma-separated list of changed deployment names to stdout, and (if running inside GitHub Actions) writes `DEPLOYMENT_NAMES`, `NEW_OR_MODIFIED_DEPLOYMENT_NAMES`, and `REMOVED_DEPLOYMENT_NAMES` to `GITHUB_ENV`.
+
+`--modified-by` accepts:
+- `pull_request` — compares your local working tree against the fetched base branch (use during an open MR/PR).
+- `push` or `pull_request_target` — compares `HEAD~1` against `HEAD` (use after a merge to a protected branch).
+
+### 2. Apply deployments
+
+```bash
+python -m prefect_deployments_toolkit \
+  --deployment-names "flow_a,flow_b" \
+  --enable-schedule false \
+  --tag dev \
+  --reference feature-branch-1 \
+  --repo-name my-flows-repo \
+  --custom-image "" \
+  --deployments-dir deployments \
+  --dev-work-pool my-dev-work-pool \
+  --backend rest \
+  --enforce-unique-deployment-names false
+```
+
+## Expected Repository Layout
+
+```bash
+deployments/
+├── prefect_base.yaml # shared config merged into every deployment
+├── flow_a.yaml
+├── flow_b.yaml
+└── ...
+```
+
+
+Each deployment YAML file must declare a `deployments:` list with at least a `name` and `entrypoint` key, following the standard Prefect deployment YAML schema.
+
+## Backends
+
+| Backend | How it works | When to use |
+|---|---|---|
+| `cli` | Shells out to `prefect deploy` | Simplest, matches local `prefect deploy` behavior exactly |
+| `rest` | Talks directly to the Prefect Cloud REST API | Faster for many concurrent deployments, avoids CLI subprocess overhead |
+
+## Environment Variables
+
+| Variable | Required | Purpose |
+|---|---|---|
+| `PREFECT_API_URL` | Yes | Full Prefect Cloud/server API base URL |
+| `PREFECT_API_KEY` | Yes | API key for authentication |
+
+## License
+
+Licensed under [PolyForm Noncommercial 1.0.0](https://polyformproject.org/licenses/noncommercial/1.0.0). You may view, use, and modify this software for noncommercial purposes. Commercial use — including building products, services, or automation on top of it — requires a separate license. Contact [your contact info] for commercial licensing inquiries.
+
+## Contributing
+
+Issues and pull requests are welcome for noncommercial use cases. Please open an issue before submitting a large PR to discuss scope.

prefect_deployments_toolkit-0.0.1/README.md

@@ -0,0 +1,90 @@
+# Prefect Deployments Toolkit
+
+A lightweight CLI toolkit for managing Prefect deployment lifecycles in CI/CD pipelines. It detects deployments that were added, modified, or removed between two git references, and applies (creates, updates, or deletes) those deployments against Prefect Cloud or a self-hosted Prefect server — via either the Prefect CLI or direct REST API calls.
+
+Built for teams running many Prefect flows out of a monorepo, where each deployment is defined in its own YAML file alongside a shared `prefect_base.yaml`, and CI needs to figure out *which* deployments actually changed before re-registering them.
+
+## Features
+
+- **Change detection** — diff deployments between two git refs (a merge request source vs. target branch, or `HEAD~1` vs. `HEAD` after a merge) and get back exactly which deployments were added, modified, or removed.
+- **Unified push / pull-request logic** — one code path handles both `pull_request` (compare local files against a fetched base branch) and `push`/`pull_request_target` (compare `HEAD~1` against `HEAD`) event styles.
+- **Dual deploy backends** — apply deployments using the `prefect` CLI as a subprocess, or bypass it entirely with direct Prefect Cloud REST API calls for faster, more controllable deploys.
+- **Dev/prod environment overrides** — automatic name prefixing, work pool substitution, and schedule pausing for dev environments.
+- **Concurrent deployment application** — apply multiple deployments in parallel with clean, non-interleaved log output per deployment.
+- **Duplicate deployment name detection** — warns (or optionally cleans up) when the same deployment name resolves to more than one flow.
+
+## Installation
+
+```bash
+pip install prefect-deployments-toolkit
+```
+
+Requires Python >= 3.10.
+
+## Usage
+
+### 1. Detect modified deployments
+
+```bash
+python -m prefect_deployments_toolkit.get_modified_deployments \
+  --modified-by push \
+  --base-ref main \
+  --deployments-dir deployments
+```
+
+Prints a comma-separated list of changed deployment names to stdout, and (if running inside GitHub Actions) writes `DEPLOYMENT_NAMES`, `NEW_OR_MODIFIED_DEPLOYMENT_NAMES`, and `REMOVED_DEPLOYMENT_NAMES` to `GITHUB_ENV`.
+
+`--modified-by` accepts:
+- `pull_request` — compares your local working tree against the fetched base branch (use during an open MR/PR).
+- `push` or `pull_request_target` — compares `HEAD~1` against `HEAD` (use after a merge to a protected branch).
+
+### 2. Apply deployments
+
+```bash
+python -m prefect_deployments_toolkit \
+  --deployment-names "flow_a,flow_b" \
+  --enable-schedule false \
+  --tag dev \
+  --reference feature-branch-1 \
+  --repo-name my-flows-repo \
+  --custom-image "" \
+  --deployments-dir deployments \
+  --dev-work-pool my-dev-work-pool \
+  --backend rest \
+  --enforce-unique-deployment-names false
+```
+
+## Expected Repository Layout
+
+```bash
+deployments/
+├── prefect_base.yaml # shared config merged into every deployment
+├── flow_a.yaml
+├── flow_b.yaml
+└── ...
+```
+
+
+Each deployment YAML file must declare a `deployments:` list with at least a `name` and `entrypoint` key, following the standard Prefect deployment YAML schema.
+
+## Backends
+
+| Backend | How it works | When to use |
+|---|---|---|
+| `cli` | Shells out to `prefect deploy` | Simplest, matches local `prefect deploy` behavior exactly |
+| `rest` | Talks directly to the Prefect Cloud REST API | Faster for many concurrent deployments, avoids CLI subprocess overhead |
+
+## Environment Variables
+
+| Variable | Required | Purpose |
+|---|---|---|
+| `PREFECT_API_URL` | Yes | Full Prefect Cloud/server API base URL |
+| `PREFECT_API_KEY` | Yes | API key for authentication |
+
+## License
+
+Licensed under [PolyForm Noncommercial 1.0.0](https://polyformproject.org/licenses/noncommercial/1.0.0). You may view, use, and modify this software for noncommercial purposes. Commercial use — including building products, services, or automation on top of it — requires a separate license. Contact [your contact info] for commercial licensing inquiries.
+
+## Contributing
+
+Issues and pull requests are welcome for noncommercial use cases. Please open an issue before submitting a large PR to discuss scope.

prefect_deployments_toolkit-0.0.1/pyproject.toml

@@ -0,0 +1,40 @@
+[project]
+name = "prefect-deployments-toolkit"
+version = "0.0.1"
+description = "CLI toolkit for detecting and applying Prefect deployment changes in CI/CD pipelines"
+readme = "README.md"
+license = { text = "PolyForm-Noncommercial-1.0.0" }
+requires-python = ">=3.10"
+authors = [
+    { name = "k-wolski", email = "kwolski@dyvenia.com" }
+]
+keywords = ["prefect", "deployment", "ci-cd", "gitlab-ci", "workflow-orchestration"]
+classifiers = [
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Operating System :: OS Independent",
+    "Topic :: Software Development :: Build Tools",
+    "Topic :: System :: Systems Administration",
+]
+dependencies = [
+    "httpx>=0.27",
+    "pyyaml>=6.0",
+    "prefect>=3.0,<4",
+]
+
+[project.urls]
+Repository = "https://github.com/dyvenia/prefect-deployments-toolkit"
+Issues = "https://github.com/dyvenia/prefect-deployments-toolkit/issues"
+
+[project.scripts]
+prefect-deployments-toolkit = "prefect_deployments_toolkit.__main__:main"
+
+[build-system]
+requires = ["hatchling", "hatch-vcs"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/prefect_deployments_toolkit"]

prefect_deployments_toolkit-0.0.1/src/prefect_deployments_toolkit/__main__.py

@@ -0,0 +1,145 @@
+"""Entry point: parse args and apply all deployments concurrently.
+
+Usage:
+python -m apply_deployments \
+    --deployment-names "hello_world3,hello_world_4" \
+    --enable-schedule false \
+    --tag dev \
+    --reference feature_branch1 \
+    --repo-name edp-flows \
+    --custom-image "" \
+    --deployments-dir prefect/deployments \
+    --dev-work-pool lapp-dev-work-pool-prefect3 \
+    --backend cli \
+    --enforce-unique-deployment-names false
+"""
+
+import argparse
+import logging
+import sys
+from concurrent.futures import ThreadPoolExecutor, as_completed
+from pathlib import Path
+
+from .deployment import DeploymentContext, apply_single_deployment
+from .log_buffer import buffered_deployment_log
+
+logger = logging.getLogger(__name__)
+
+MAX_WORKERS = 8
+
+
+def _parse_args() -> argparse.Namespace:
+    parser = argparse.ArgumentParser(description="Apply Prefect deployments.")
+    parser.add_argument("--deployment-names", required=True,
+                         help="Comma-separated list of deployment names.")
+    parser.add_argument("--enable-schedule", required=True,
+                         choices=["true", "false"],
+                         help="Whether to enable schedules after deploy.")
+    parser.add_argument("--tag", required=True,
+                         help="Image/environment tag (e.g. 'dev', 'v1.2.3').")
+    parser.add_argument("--reference", required=True,
+                         help="Git branch or tag reference (e.g. 'main', 'feature_branch1').")
+    parser.add_argument("--repo-name", required=True,
+                         help="Repository name used in job variable paths.")
+    parser.add_argument("--custom-image", default="",
+                         help="Full custom image reference, or empty string to use pool default.")
+    parser.add_argument("--deployments-dir", default="deployments",
+                         help="Path to the deployments directory.")
+    parser.add_argument("--dev-work-pool", default="",
+                         help="Dev work pool name. When set with --tag=dev, activates dev overrides.")
+    parser.add_argument("--max-workers", type=int, default=MAX_WORKERS,
+                         help=f"Max concurrent deployments (default: {MAX_WORKERS}).")
+    parser.add_argument("--backend", default="cli", choices=["cli", "rest"],
+                         help="Deployment backend: 'cli' (prefect CLI, default) or "
+                              "'rest' (direct Prefect Cloud REST API calls).")
+    parser.add_argument("--enforce-unique-deployment-names", default="false",
+                        choices=["true", "false"],
+                        help=(
+                            "If false (default), only WARN in logs when a deployment name is used by"
+                            "more than one flow — nothing is deleted. If true, delete every duplicate"
+                            "deployment record except the one matching the flow currently resolved from"
+                            "its entrypoint, enforcing globally unique deployment names."
+                        ))
+    return parser.parse_args()
+
+
+def _run_deployment(
+    deployment_name: str,
+    index: int,
+    total: int,
+    ctx: DeploymentContext,
+) -> str | None:
+    """Run a single deployment inside a buffered log context.
+
+    Returns the deployment_name if it failed, None on success.
+    """
+    separator = "#" * 60
+    with buffered_deployment_log(deployment_name):
+        logger.info("%s [%d/%d] %s %s", separator, index, total, deployment_name, separator)
+        try:
+            apply_single_deployment(deployment_name, ctx)
+            logger.info(">>> DONE [%d/%d] %s", index, total, deployment_name)
+            return None
+        except Exception as exc:  # noqa: BLE001
+            logger.error(">>> FAILED [%d/%d] %s: %s", index, total, deployment_name, exc)
+            return deployment_name
+
+
+def main() -> None:
+    logging.basicConfig(
+        level=logging.INFO,
+        format="%(asctime)s [%(levelname)s] %(message)s",
+    )
+    args = _parse_args()
+    names = [n.strip() for n in args.deployment_names.split(",") if n.strip()]
+
+    if not names:
+        logger.error("No deployment names provided.")
+        sys.exit(1)
+
+    ctx = DeploymentContext(
+        deployment_names=names,
+        enable_schedule=args.enable_schedule == "true",
+        tag=args.tag,
+        reference=args.reference,
+        repo_name=args.repo_name,
+        custom_image=args.custom_image,
+        deployments_dir=Path(args.deployments_dir),
+        dev_prefect_work_pool_name=args.dev_work_pool,
+        backend=args.backend,
+        enforce_unique_deployment_names=args.enforce_unique_deployment_names == "true",
+    )
+
+    total = len(names)
+    workers = min(args.max_workers, total)
+    logger.info(
+        "Applying %d deployment(s) with up to %d concurrent workers (backend=%s).",
+        total, workers, ctx.backend,
+    )
+
+    failed: list[str] = []
+
+    with ThreadPoolExecutor(max_workers=workers) as executor:
+        futures = {
+            executor.submit(_run_deployment, name, i, total, ctx): name
+            for i, name in enumerate(names, start=1)
+        }
+        for future in as_completed(futures):
+            result = future.result()  # re-raises only unexpected executor errors
+            if result is not None:
+                failed.append(result)
+
+    if failed:
+        logger.error(
+            "%d deployment(s) failed: %s",
+            len(failed),
+            ", ".join(failed),
+        )
+        sys.exit(1)
+
+    logger.info("All %d deployment(s) applied successfully.", total)
+
+
+if __name__ == "__main__":
+    main()
+