add-new-command

Add a new CLI command by following an outside-in approach that scaffolds the presentation layer, defines application handler contracts, and outlines domain considerations for the Torrust Deployer. This structured process ensures scalable and safe command development across presentation, application, and testing phases.

The outside-in approach for CLI command development starts with presentation layer scaffolding, then defines application handler contracts, and finally addresses domain considerations. It enforces evaluation of dependencies, components, and safety considerations to ensure consistent interfaces and robust command scaffolding.

Structure testing for a new deployer command by following the guided process that includes E2E planning and testing phase definitions. This ensures your new commands like validate, render, or backup are safely validated through repeatable deployments before integration.

Yes, you need to update documentation when adding a new command to the Torrust Deployer. The command development process explicitly includes documentation guidance to accelerate safe, repeatable deployments and standardize your contributions with recommended commit messaging.

Yes, you can use quick-start templates to scaffold deployer commands. The guide provides templates and recommended commit messaging to standardize contributions, ensuring consistent interfaces and robust scaffolding for new commands like validate, render, or backup.

Safety considerations when developing CLI commands include evaluating dependencies, components, and potential risks before implementation. The guide enforces this evaluation while outlining documentation and workflows to guarantee safe, repeatable deployments for the Torrust Deployer.