Deploy Migration

Move from praisonai.deploy to the standalone praisonai-deploy package

praisonai-deploy is a standalone tier-2 package. Existing praisonai.deploy imports keep working through compatibility shims.

python
# New code
from praisonai_deploy import Deploy

# Still works (compatibility shim)
from praisonai.deploy import Deploy
Diagram

shim

praisonai.deploy

praisonai_deploy

Quick Start

  1. Update your import
    python
    from praisonai_deploy import Deploy
  2. Everything else stays the same
    python
    deploy = Deploy.from_yaml("agents.yaml")
    result = deploy.deploy()

Import Mapping

Old pathNew path
from praisonai.deploy import Deployfrom praisonai_deploy import Deploy
from praisonai.deploy import DeployConfigfrom praisonai_deploy import DeployConfig
praisonai.cli.commands.deployforwarded to the new Typer subcommands

Compatibility Coverage

The extraction preserves existing imports through alias shims:

  • praisonai.deploy forwards to praisonai_deploy.
  • praisonai.cli.commands.deploy forwards to the new Typer subcommands.
  • Legacy scheduler imports continue to resolve.
  • praisonai-code calls into deploy through a bridge, without a hard dependency.

These are verified by regression gates:

  • scripts/check_c14_deploy_imports.sh
  • test_c14_deploy_backward_compat.py (18 passing)
  • praisonai-deploy unit tests (115 passing)

Install

Standalone
pip install praisonai-deploy
Full umbrella
pip install "praisonai[deploy]"

The full praisonai umbrella keeps the wrapper shims installed, so existing scripts run unchanged.


Best Practices

Migrate imports gradually

The shims mean you can update imports file by file without breaking anything in between.

Install the standalone package for slim deploys

pip install praisonai-deploy gives you the deploy surface without pulling the full wrapper.


Related