Struct RenderCommandHandler 

pub struct RenderCommandHandler { /* private fields */ }

RenderCommandHandler generates deployment artifacts without deployment

This command handler provides a way to preview or generate deployment artifacts (docker-compose files, Ansible playbooks, tracker config, etc.) without executing any infrastructure operations.

State Management

• Created State Only: Command works for environments in “Created” state
• Already Provisioned: Returns informational result (not error) with artifacts location
• No State Modification: Does not change environment state or execute deployments

Dual Input Modes

1. Environment Name Mode: Loads existing environment from repository
2. Config File Mode: Parses configuration file directly (no env creation)

Workflow

1. Determine input mode (env-name or env-file)
2. Load/parse configuration
3. Validate state (Created only for existing environments)
4. Parse target IP address
5. Render all deployment templates to build/{env}/ directory

Implementations

impl RenderCommandHandler

pub fn new(repository: Arc<dyn EnvironmentRepository>) -> Self

Create a new RenderCommandHandler

pub async fn execute( &self, input_mode: RenderInputMode, target_ip: &str, output_dir: &Path, force: bool, working_dir: &Path, ) -> Result<RenderResult, RenderCommandHandlerError>

Execute the render workflow

Arguments

• input_mode - Source of configuration (env-name or env-file)
• target_ip - Target instance IP address (always required)
• output_dir - Output directory for generated artifacts
• force - Whether to overwrite existing output directory
• working_dir - Working directory for resolving relative paths

Returns

Returns RenderResult with paths to generated artifacts

Errors

Returns an error if:

• Environment not found (env-name mode)
• Config file not found or invalid (env-file mode)
• IP address parsing fails
• Output directory exists and force is false
• Template rendering fails