Deploy Python Project
Read .copier-answers.yml and deploy/README.md first; they identify the target, commands, environment variables, and any generated IaC.
Workflow
- Run the full project quality gates from
project-workflow. - Build the generated Dockerfile locally. Start the image with explicit environment variables and verify its documented health route.
- Validate target configuration as structured JSON, TOML, YAML, Python, or HCL. Never infer that a successful parse proves cloud readiness.
- For Pulumi, run a preview before update. For Terraform, run format, init without changing remote state where possible, validate, and plan before apply.
- Confirm account, region, project, service name, expected cost boundary, secrets source, and rollback strategy before creating or changing remote resources.
- Deploy with the command documented in
deploy/README.md, then verify the remote health route and one representative request. - Report the deployed revision, endpoint, verification evidence, and any manual DNS or secret-management step.
Safety
- Do not deploy, apply IaC, delete resources, or expose a public endpoint without explicit authorization.
- Do not embed provider credentials in images, configuration, logs, or Git.
- Keep the Docker path usable even when the selected managed platform provides a native adapter.