refactor: remove verbose parameter and replace with tracing-based logging

- Remove verbose: bool fields from all structs (Config, TofuTemplateRenderer, AnsibleTemplateRenderer, CommandExecutor)
- Update all constructors to remove verbose parameters
- Update CLI documentation to reflect removal of --verbose flag
- Rename test functions to accurately reflect new tracing-based approach
- Add Default implementations for CommandExecutor and LxdClient to satisfy clippy
- Update GitHub workflows to remove outdated --verbose references
- Update project documentation to use RUST_LOG environment variable instead of CLI verbose flags

The tracing crate provides better log level control through RUST_LOG environment variable,
making the manual verbose boolean parameter redundant.

Author: josecelano

.github/workflows/test-e2e.yml

@@ -57,10 +57,10 @@ jobs:
 
       - name: Run E2E test
         run: |
-          # Run the E2E test with verbose output for better debugging
+          # Run the E2E test with debug logging for better debugging
           # Use sudo -E and preserve PATH to ensure cargo is accessible
           echo "🚀 Starting E2E test at $(date)"
-          sudo -E env "PATH=$PATH" cargo run --bin e2e-tests -- --verbose
+          sudo -E env "PATH=$PATH" cargo run --bin e2e-tests
           echo "✅ E2E test completed at $(date)"
         env:
           # Preserve environment variables for the E2E test

README.md

@@ -121,8 +121,8 @@ cargo run --bin e2e-tests
 # Keep the test environment after completion
 cargo run --bin e2e-tests -- --keep
 
-# Run with verbose output
-cargo run --bin e2e-tests -- --verbose
+# Use custom templates directory
+cargo run --bin e2e-tests -- --templates-dir ./custom/templates
 
 # See all available options
 cargo run --bin e2e-tests -- --help

docs/console-commands.md

@@ -71,7 +71,10 @@ torrust-deploy check [OPTIONS]
 **Options**:
 
 - `--fix` - Attempt to auto-install missing tools
-- `--verbose` - Show detailed validation steps
+
+**Environment Variables**:
+
+- `RUST_LOG=debug` - Show detailed validation steps via tracing
 
 **Example Output**:
 
@@ -141,7 +144,10 @@ torrust-deploy provision <environment> [OPTIONS]
 
 - `--auto-approve` - Skip confirmation prompts
 - `--keep-on-failure` - Don't cleanup on provision failure
-- `--verbose` - Detailed provisioning logs
+
+**Environment Variables**:
+
+- `RUST_LOG=debug` - Detailed provisioning logs via tracing
 
 ---
 
@@ -333,7 +339,8 @@ torrust-deploy destroy <environment> [OPTIONS]
 
 ## Notes
 
-- All commands should support `--verbose` flag for detailed output
+- All commands use the tracing crate for logging (control verbosity with `RUST_LOG` environment variable)
+- Set `RUST_LOG=debug` for detailed output, `RUST_LOG=info` for standard output
 - Configuration should be environment-aware once multi-env support is added
 - Error handling should be consistent across all commands
 - Each command should validate prerequisites before execution

docs/current-implementation.md

@@ -51,7 +51,7 @@ These features are fully working in the E2E test environment:
 
 - **`Config` struct**: Centralizes all deployment parameters
 - **Path Management**: Handles SSH keys, templates, build directories
-- **Runtime Parameters**: Verbose mode, cleanup behavior, provider settings
+- **Runtime Parameters**: Cleanup behavior, provider settings, SSH configuration
 
 #### Service Container
 

docs/deployment-overview.md

@@ -74,7 +74,7 @@ torrust-deploy status           # List all environments (future)
 
 ```bash
 # Simulate current working functionality through E2E tests
-cargo run --bin e2e-tests --verbose
+cargo run --bin e2e-tests
 
 # This runs equivalent to:
 # provision: Creates LXD container with OpenTofu

docs/e2e-testing.md

@@ -21,20 +21,23 @@ cargo run --bin e2e-tests
 ### Command Line Options
 
 - `--keep` - Keep the test environment after completion (useful for debugging)
-- `--verbose` - Enable verbose output to see detailed execution steps
+- `--templates-dir` - Specify custom templates directory path
 - `--help` - Show help information
 
 ### Examples
 
 ```bash
-# Run with verbose output
-cargo run --bin e2e-tests -- --verbose
+# Run basic e2e tests
+cargo run --bin e2e-tests
 
 # Keep environment for debugging
 cargo run --bin e2e-tests -- --keep
 
+# Use custom templates directory
+cargo run --bin e2e-tests -- --templates-dir ./custom/templates
+
 # Combine options
-cargo run --bin e2e-tests -- --verbose --keep
+cargo run --bin e2e-tests -- --keep --templates-dir ./custom/templates
 ```
 
 ## 📋 Test Sequence
@@ -158,7 +161,7 @@ GitHub Actions runners sometimes experience intermittent network connectivity pr
 Use the `--keep` flag to inspect the environment after test completion:
 
 ```bash
-cargo run --bin e2e-tests -- --keep --verbose
+cargo run --bin e2e-tests -- --keep
 
 # After test completion, connect to the container:
 lxc exec torrust-vm -- /bin/bash

docs/e2e-tests-refactoring-plan.md

@@ -542,9 +542,9 @@ The current implementation executes most operations sequentially:
 ```rust
 async fn run_parallel_validations(&self, container_ip: &str) -> Result<()> {
     let validators = vec![
-        CloudInitValidator::new(&self.config.ssh_key_path, &self.config.ssh_username, self.config.verbose),
-        DockerValidator::new(&self.config.ssh_key_path, &self.config.ssh_username, self.config.verbose),
-        DockerComposeValidator::new(&self.config.ssh_key_path, &self.config.ssh_username, self.config.verbose),
+        CloudInitValidator::new(&self.config.ssh_key_path, &self.config.ssh_username, container_ip),
+        DockerValidator::new(&self.config.ssh_key_path, &self.config.ssh_username, container_ip),
+        DockerComposeValidator::new(&self.config.ssh_key_path, &self.config.ssh_username, container_ip),
     ];
 
     let validation_tasks: Vec<_> = validators

src/actions/cloud_init.rs

@@ -17,10 +17,9 @@ impl CloudInitValidator {
     /// * `ssh_key_path` - Path to the SSH private key file
     /// * `username` - SSH username to use for connections
     /// * `host_ip` - IP address of the target host
-    /// * `verbose` - Whether to enable verbose SSH output
     #[must_use]
-    pub fn new(ssh_key_path: &Path, username: &str, host_ip: IpAddr, verbose: bool) -> Self {
-        let ssh_client = SshClient::new(ssh_key_path, username, host_ip, verbose);
+    pub fn new(ssh_key_path: &Path, username: &str, host_ip: IpAddr) -> Self {
+        let ssh_client = SshClient::new(ssh_key_path, username, host_ip);
         Self { ssh_client }
     }
 }

src/actions/docker.rs

@@ -17,10 +17,9 @@ impl DockerValidator {
     /// * `ssh_key_path` - Path to the SSH private key file
     /// * `username` - SSH username to use for connections
     /// * `host_ip` - IP address of the target host
-    /// * `verbose` - Whether to enable verbose SSH output
     #[must_use]
-    pub fn new(ssh_key_path: &Path, username: &str, host_ip: IpAddr, verbose: bool) -> Self {
-        let ssh_client = SshClient::new(ssh_key_path, username, host_ip, verbose);
+    pub fn new(ssh_key_path: &Path, username: &str, host_ip: IpAddr) -> Self {
+        let ssh_client = SshClient::new(ssh_key_path, username, host_ip);
         Self { ssh_client }
     }
 }

src/actions/docker_compose.rs

@@ -17,10 +17,9 @@ impl DockerComposeValidator {
     /// * `ssh_key_path` - Path to the SSH private key file
     /// * `username` - SSH username to use for connections
     /// * `host_ip` - IP address of the target host
-    /// * `verbose` - Whether to enable verbose SSH output
     #[must_use]
-    pub fn new(ssh_key_path: &Path, username: &str, host_ip: IpAddr, verbose: bool) -> Self {
-        let ssh_client = SshClient::new(ssh_key_path, username, host_ip, verbose);
+    pub fn new(ssh_key_path: &Path, username: &str, host_ip: IpAddr) -> Self {
+        let ssh_client = SshClient::new(ssh_key_path, username, host_ip);
         Self { ssh_client }
     }
 }