Preflight and deployment readiness

Preflight and deployment readiness in managed mode

In managed mode, infrastructure ownership is externalized, but deployment quality is still process-driven. This page defines what to validate before each run.

Purpose and audience

For operators and teams executing production changes via managed workflows that need predictable standards on every run.

Prerequisites

• Active workspace with assigned team owner,
• selected template stack matches the change goal,
• defined approval policy and approver,
• basic familiarity with guided deployment.

Step-by-step

1. Define change scope: confirm what will change, which workspace and servers are affected, and who approves it.
2. Fill inputs: complete all required fields (especially domain, stack flags, SSL and secrets strategy).
3. Run preflight: let LaraDep execute preflight checks and explicitly resolve warnings and failed checks.
4. Window and communication: verify maintenance window and fallback contacts before running.
5. Execution: start with the minimal safe tag set before adding optional steps.
6. Post-run validation: confirm target availability, TLS status, and successful run record.

Pre-run checklist

• Is scope confirmed and ownership assigned?
• Is there a ticketing/decision reference and verifier?
• Did preflight pass critical checks without blockers?
• Are communication and rollback contacts prepared?
• Do you have a post-run note template for review?

Common mistakes

• Running changes without explicit ownership,
• Treating warnings as harmless without context,
• Skipping approval windows,
• Missing trace from request to approved run.

Next steps

• After baseline validation, move to managed operations and governance.
• If you are before first production run, review managed onboarding checklist.
• Close the loop through runbook and governance and update operational notes.

Next step: Continue with first deployment and production checklist.