Deploy Tasks Bundle Laravel Package

Product Decisions This Supports

• Adoption and roadmap for deployment-task tracking: v0.6.0 adds deploytasks:prune, addressing a common lifecycle gap: records left behind when tasks or group slots are removed from code. This supports decisions to keep deploy-task execution history in the package rather than building custom cleanup scripts.
• Build vs. buy/adopt: The command’s --dry-run, interactive confirmation, --force/--no-interaction opt-outs, --group filtering, and shell completion make it suitable for routine operator use, reducing the need for bespoke pruning tooling around JSON/filesystem or DBAL storage backends.
• Safe codebase evolution: Product and engineering can refactor or retire deployment tasks and group slots with a documented cleanup path, lowering the risk of stale operational records accumulating after releases.
• Data retention and operational hygiene: Teams can inspect orphaned records before deletion, apply scoped cleanup by group, and automate non-interactive pruning where appropriate.
• Release/upgrade planning: The new command is a maintenance feature, not a breaking change; it can be introduced as an operational safeguard without requiring a broader migration.

When to Consider This Package

Consider adopting this package when:

• Your Laravel application persists deploy task execution records using the supported JSON/filesystem or DBAL storage backends.
• Deploy tasks or group slots are expected to be renamed, removed, or reorganized over time, creating orphaned execution records.
• Operators need a safe, inspectable cleanup workflow with --dry-run, confirmation prompts, scoped --group filtering, and automation-friendly flags.
• You want to avoid custom scripts or manual storage edits to maintain deployment history hygiene.
• Shell completion and an Artisan-native command fit your existing operational tooling.

Look elsewhere or defer when:

• You do not persist deploy task execution records, or cleanup is already handled by automated retention policies.
• You require policy-driven TTL deletion, compliance-grade audit retention, multi-tenant retention rules, or database-native cascading cleanup beyond this command’s scope.
• You are not using Laravel/PHP or the supported storage backends.
• Your deployment system is simple enough that orphaned record cleanup is not an operational concern.

How to Pitch It (Stakeholders)

For executives: v0.6.0 improves operational maturity by adding a safe, built-in way to clean up stale deployment-task execution records. This reduces manual maintenance, lowers the risk of storage bloat, and supports ongoing codebase changes without accumulating orphaned operational data.

For engineering: The new deploytasks:prune command inspects and prunes orphaned deploy task execution records across JSON/filesystem and DBAL storage. It supports --dry-run, interactive confirmation with --force/--no-interaction, --group filtering, and shell completion. This gives teams an Artisan-native, auditable cleanup path when tasks or group slots are removed from code, reducing reliance on one-off scripts.