feat: [#220] Tracker Slice - Release and Run Commands

.cargo/config.toml

@@ -1,8 +1,8 @@
 [alias]
 lint = "run --bin linter all"
-e2e-full = "run --bin e2e-tests-full"
-e2e-provision = "run --bin e2e-provision-tests"
-e2e-config = "run --bin e2e-config-and-release-tests"
+e2e-complete = "run --bin e2e-complete-workflow-tests"
+e2e-infrastructure = "run --bin e2e-infrastructure-lifecycle-tests"
+e2e-deployment = "run --bin e2e-deployment-workflow-tests"
 cov = "llvm-cov"
 cov-check = "llvm-cov --all-features --workspace --fail-under-lines 70"
 cov-lcov = "llvm-cov --lcov --output-path=./.coverage/lcov.info"

.github/workflows/test-e2e-config.yml → .github/workflows/test-e2e-deployment.yml

@@ -1,5 +1,5 @@
 ---
-name: E2E Configuration Tests
+name: E2E Deployment Workflow Tests
 
 # This workflow tests ONLY software configuration, release, and run phases
 # using Docker containers. It does NOT test infrastructure provisioning
@@ -22,7 +22,7 @@ on:
   workflow_dispatch: # Allow manual triggering
 
 jobs:
-  e2e-config-and-release-tests:
+  e2e-deployment-workflow-tests:
     runs-on: ubuntu-latest
     timeout-minutes: 45 # Timeout for complete configuration testing with software installation
 
@@ -62,16 +62,16 @@ jobs:
           chmod 600 fixtures/testing_rsa
           ls -la fixtures/testing_rsa
 
-      - name: Build E2E configuration and release tests binary
+      - name: Build E2E deployment workflow tests binary
         run: |
-          cargo build --bin e2e-config-and-release-tests --release
+          cargo build --bin e2e-deployment-workflow-tests --release
 
-      - name: Run E2E configuration and release test
+      - name: Run E2E deployment workflow test
         run: |
-          # Run the E2E configuration and release test with debug logging for better debugging
-          echo "🚀 Starting E2E configuration and release test at $(date)"
-          cargo run --bin e2e-config-and-release-tests
-          echo "✅ E2E configuration and release test completed at $(date)"
+          # Run the E2E deployment workflow test with debug logging for better debugging
+          echo "🚀 Starting E2E deployment workflow test at $(date)"
+          cargo run --bin e2e-deployment-workflow-tests
+          echo "✅ E2E deployment workflow test completed at $(date)"
         env:
           # Preserve environment variables for the E2E test
           RUST_LOG: debug
@@ -113,8 +113,8 @@ jobs:
           # properly (e.g., if the test was abruptly halted). Under normal circumstances,
           # the testcontainers crate should automatically clean up containers when tests finish.
 
-          # Clean up the specific container created for e2e-config tests
-          docker rm -f torrust-tracker-vm-e2e-config 2>/dev/null || echo "Container torrust-tracker-vm-e2e-config not found or already removed"
+          # Clean up the specific container created for e2e-deployment tests
+          docker rm -f torrust-tracker-vm-e2e-deployment 2>/dev/null || echo "Container torrust-tracker-vm-e2e-deployment not found or already removed"
 
           # Clean up any test images if needed
           docker images --filter "reference=torrust-provisioned-instance*" -q | xargs -r docker rmi -f || echo "No test images to remove"
@@ -126,9 +126,9 @@ jobs:
           docker ps -a
 
           echo "=== Test Summary ==="
-          echo "E2E configuration test workflow completed"
+          echo "E2E deployment workflow test completed"
           if [ "${{ job.status }}" = "success" ]; then
-            echo "✅ All configuration tests passed successfully"
+            echo "✅ All deployment workflow tests passed successfully"
           else
-            echo "❌ Some configuration tests failed - check logs above"
+            echo "❌ Some deployment workflow tests failed - check logs above"
           fi

.github/workflows/test-e2e-provision.yml → .github/workflows/test-e2e-infrastructure.yml

@@ -1,4 +1,4 @@
-name: E2E Provision and Destroy Tests
+name: E2E Infrastructure Lifecycle Tests
 
 # This workflow tests infrastructure provisioning and destruction (creating and destroying VMs/containers)
 # It does NOT test software configuration/installation to avoid GitHub Actions
@@ -18,7 +18,7 @@ on:
   workflow_dispatch: # Allow manual triggering
 
 jobs:
-  e2e-provision-tests:
+  e2e-infrastructure-lifecycle-tests:
     runs-on: ubuntu-latest
     timeout-minutes: 30 # Reduced timeout since we're not installing software
 
@@ -48,17 +48,17 @@ jobs:
           tofu version
           cargo --version
 
-      - name: Build E2E provision and destroy tests binary
+      - name: Build E2E infrastructure lifecycle tests binary
         run: |
-          cargo build --bin e2e-provision-and-destroy-tests --release
+          cargo build --bin e2e-infrastructure-lifecycle-tests --release
 
-      - name: Run E2E provision and destroy test
+      - name: Run E2E infrastructure lifecycle test
         run: |
-          # Run the E2E provision and destroy test with debug logging for better debugging
+          # Run the E2E infrastructure lifecycle test with debug logging for better debugging
           # Use sudo -E and preserve PATH to ensure cargo is accessible
-          echo "🚀 Starting E2E provision and destroy test at $(date)"
-          sudo -E env "PATH=$PATH" cargo run --bin e2e-provision-and-destroy-tests
-          echo "✅ E2E provision and destroy test completed at $(date)"
+          echo "🚀 Starting E2E infrastructure lifecycle test at $(date)"
+          sudo -E env "PATH=$PATH" cargo run --bin e2e-infrastructure-lifecycle-tests
+          echo "✅ E2E infrastructure lifecycle test completed at $(date)"
         env:
           # Preserve environment variables for the E2E test
           RUST_LOG: debug
@@ -68,18 +68,18 @@ jobs:
         run: |
           echo "=== Infrastructure Outputs ==="
           # Only check outputs if build directory still exists (it may be cleaned up by DestroyCommand)
-          if [ -d "build/e2e-provision/tofu/lxd" ]; then
-            cd build/e2e-provision/tofu/lxd
+          if [ -d "build/e2e-infrastructure/tofu/lxd" ]; then
+            cd build/e2e-infrastructure/tofu/lxd
             sudo -E tofu output || echo "No outputs available"
           else
             echo "Build directory not found (likely cleaned up by DestroyCommand)"
           fi
 
           echo "=== Container Status ==="
-          sudo lxc list torrust-tracker-vm-e2e-provision || echo "Container not found"
+          sudo lxc list torrust-tracker-vm-e2e-infrastructure || echo "Container not found"
 
           # Check if the container has an IP address before proceeding
-          sudo lxc info torrust-tracker-vm-e2e-provision || echo "Container info not available"
+          sudo lxc info torrust-tracker-vm-e2e-infrastructure || echo "Container info not available"
 
       - name: Debug information (on failure)
         if: failure()
@@ -88,8 +88,8 @@ jobs:
           sudo lxc list || echo "LXC list failed"
 
           echo "=== OpenTofu State ==="
-          if [ -d "build/e2e-provision/tofu/lxd" ]; then
-            cd build/e2e-provision/tofu/lxd
+          if [ -d "build/e2e-infrastructure/tofu/lxd" ]; then
+            cd build/e2e-infrastructure/tofu/lxd
             sudo -E tofu show || echo "No state to show"
           else
             echo "No OpenTofu state directory found"
@@ -108,18 +108,18 @@ jobs:
           echo "Test failed - attempting emergency cleanup..."
 
           # Try OpenTofu cleanup only if build directory still exists
-          if [ -d "build/e2e-provision/tofu/lxd" ]; then
+          if [ -d "build/e2e-infrastructure/tofu/lxd" ]; then
             echo "Found OpenTofu state directory, attempting tofu destroy..."
-            cd build/e2e-provision/tofu/lxd
+            cd build/e2e-infrastructure/tofu/lxd
             sudo -E tofu destroy -auto-approve || echo "Tofu destroy failed or nothing to destroy"
           else
             echo "No OpenTofu state directory found (likely cleaned up by DestroyCommand)"
           fi
 
           # Always attempt LXD cleanup (no working directory dependency)
           echo "Attempting LXD resource cleanup..."
-          sudo lxc delete torrust-tracker-vm-e2e-provision --force || echo "Container deletion failed or container doesn't exist"
-          sudo lxc profile delete torrust-profile-e2e-provision || echo "Profile deletion failed or profile doesn't exist"
+          sudo lxc delete torrust-tracker-vm-e2e-infrastructure --force || echo "Container deletion failed or container doesn't exist"
+          sudo lxc profile delete torrust-profile-e2e-infrastructure || echo "Profile deletion failed or profile doesn't exist"
 
       - name: Final verification
         if: always()
@@ -128,9 +128,9 @@ jobs:
           sudo lxc list
 
           echo "=== Test Summary ==="
-          echo "E2E provision and destroy test workflow completed"
+          echo "E2E infrastructure lifecycle test workflow completed"
           if [ "${{ job.status }}" = "success" ]; then
-            echo "✅ All provision and destroy tests passed successfully"
+            echo "✅ All infrastructure lifecycle tests passed successfully"
           else
-            echo "❌ Some provision and destroy tests failed - check logs above"
+            echo "❌ Some infrastructure lifecycle tests failed - check logs above"
           fi

.taplo.toml

@@ -1,5 +1,13 @@
 # Taplo configuration file for TOML formatting
 # Used by the "Even Better TOML" VS Code extension
+
+# Exclude generated and runtime folders from linting
+exclude = [
+  "build/**",
+  "data/**",
+  "envs/**",
+]
+
 [formatting]
 # Preserve blank lines that exist
 allowed_blank_lines = 1

AGENTS.md

@@ -130,10 +130,15 @@ These principles should guide all development decisions, code reviews, and featu
 - **Test**: `cargo test`
 - **Unit Tests**: When writing unit tests, follow conventions described in [`docs/contributing/testing/`](docs/contributing/testing/)
 - **E2E Tests**:
-  - `cargo run --bin e2e-tests-full` - Comprehensive tests (⚠️ **LOCAL ONLY** - cannot run on GitHub Actions due to network connectivity issues)
-  - `cargo run --bin e2e-provision-and-destroy-tests` - Infrastructure provisioning and destruction tests (GitHub runner-compatible)
-  - `cargo run --bin e2e-config-and-release-tests` - Software installation, configuration, release, and run workflow tests (GitHub runner-compatible)
-  - Pre-commit hook runs the split tests (`e2e-provision-and-destroy-tests` + `e2e-config-and-release-tests`) for GitHub Copilot compatibility
-  - See [`docs/e2e-testing.md`](docs/e2e-testing.md) for detailed information about CI limitations
+  - `cargo run --bin e2e-complete-workflow-tests` - Comprehensive tests (⚠️ **LOCAL ONLY** - cannot run on GitHub Actions due to network connectivity issues)
+  - `cargo run --bin e2e-infrastructure-lifecycle-tests` - Infrastructure provisioning and destruction tests (GitHub runner-compatible)
+  - `cargo run --bin e2e-deployment-workflow-tests` - Software installation, configuration, release, and run workflow tests (GitHub runner-compatible)
+  - Pre-commit hook runs the split tests (`e2e-infrastructure-lifecycle-tests` + `e2e-deployment-workflow-tests`) for GitHub Copilot compatibility
+  - See [`docs/e2e-testing/`](docs/e2e-testing/) for detailed information about CI limitations
+- **Manual E2E Testing**: For step-by-step manual testing with CLI commands, see [`docs/e2e-testing/manual-testing.md`](docs/e2e-testing/manual-testing.md). This guide covers:
+  - Complete manual test workflow from template creation to deployment
+  - Handling interrupted commands and state recovery
+  - Troubleshooting common issues
+  - Cleanup procedures for both application and LXD resources
 
 Follow the project conventions and ensure all checks pass.

Cargo.toml

@@ -21,16 +21,16 @@ name = "torrust-tracker-deployer"
 path = "src/main.rs"
 
 [[bin]]
-name = "e2e-tests-full"
-path = "src/bin/e2e_tests_full.rs"
+name = "e2e-complete-workflow-tests"
+path = "src/bin/e2e_complete_workflow_tests.rs"
 
 [[bin]]
-name = "e2e-config-and-release-tests"
-path = "src/bin/e2e_config_and_release_tests.rs"
+name = "e2e-deployment-workflow-tests"
+path = "src/bin/e2e_deployment_workflow_tests.rs"
 
 [[bin]]
-name = "e2e-provision-and-destroy-tests"
-path = "src/bin/e2e_provision_and_destroy_tests.rs"
+name = "e2e-infrastructure-lifecycle-tests"
+path = "src/bin/e2e_infrastructure_lifecycle_tests.rs"
 
 [[bin]]
 name = "linter"
@@ -48,6 +48,7 @@ clap = { version = "4.0", features = [ "derive" ] }
 derive_more = "0.99"
 figment = { version = "0.10", features = [ "json" ] }
 parking_lot = "0.12"
+reqwest = "0.12"
 rust-embed = "8.0"
 serde = { version = "1.0", features = [ "derive" ] }
 serde_json = "1.0"

README.md

@@ -1,4 +1,4 @@
-[![Linting](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/linting.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/linting.yml) [![Testing](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/testing.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/testing.yml) [![E2E Provision Tests](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/test-e2e-provision.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/test-e2e-provision.yml) [![E2E Config Tests](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/test-e2e-config.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/test-e2e-config.yml) [![Test LXD Container Provisioning](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/test-lxd-provision.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/test-lxd-provision.yml) [![Coverage](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/coverage.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/coverage.yml)
+[![Linting](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/linting.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/linting.yml) [![Testing](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/testing.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/testing.yml) [![E2E Infrastructure Tests](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/test-e2e-infrastructure.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/test-e2e-infrastructure.yml) [![E2E Deployment Tests](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/test-e2e-deployment.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/test-e2e-deployment.yml) [![Test LXD Container Provisioning](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/test-lxd-provision.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/test-lxd-provision.yml) [![Coverage](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/coverage.yml/badge.svg)](https://github.com/torrust/torrust-tracker-deployer/actions/workflows/coverage.yml)
 
 # Torrust Tracker Deployer
 
@@ -12,9 +12,9 @@
 > - ✅ **Hetzner Cloud support** for production deployments
 > - ✅ Development and testing workflows
 > - ✅ Multi-provider architecture (provider selection via configuration)
-> - ❌ Application deployment (Torrust Tracker stack) - coming soon
+> - ✅ **Application deployment** (Torrust Tracker stack with Docker Compose)
 >
-> 📋 **MVP Goal:** After completing the [roadmap](docs/roadmap.md), we will have a fully automated deployment solution for Torrust Tracker with complete application stack management.
+> 📋 **MVP Goal:** After completing the [roadmap](docs/roadmap.md), we will have a fully automated deployment solution for Torrust Tracker with complete application stack management and multi-cloud provider support.
 
 This Rust application provides automated deployment infrastructure for Torrust tracker projects. It supports **local development** with LXD and **production deployments** with Hetzner Cloud. The multi-provider architecture allows easy extension to additional cloud providers.
 
@@ -28,12 +28,13 @@ This Rust application provides automated deployment infrastructure for Torrust t
 - ✅ **Fast, easy to install and use** local development solution
 - ✅ **No nested virtualization dependency** (CI compatibility)
 - ✅ **Multi-provider support** (LXD for local, Hetzner Cloud for production)
+- ✅ **Application stack deployment** (Torrust Tracker with Docker Compose)
 
 **Future MVP Goals:** (See [roadmap](docs/roadmap.md))
 
 - 🔄 **Additional cloud providers** (AWS, GCP, Azure)
-- 🔄 **Application stack deployment** (Torrust Tracker with Docker Compose)
 - 🔄 **Multi-environment management**
+- 🔄 **Enhanced observability** (monitoring, alerting, metrics)
 
 ## 🔧 Local Development Approach
 
@@ -164,18 +165,18 @@ Use the E2E test binaries to run automated infrastructure tests with hardcoded e
 
 ```bash
 # Run comprehensive E2E tests (LOCAL ONLY - connectivity issues in GitHub runners)
-cargo run --bin e2e-tests-full
+cargo run --bin e2e-complete-workflow-tests
 
 # Run individual E2E test suites
-cargo run --bin e2e-config-and-release-tests      # Configuration, release, and run workflow tests
-cargo run --bin e2e-provision-and-destroy-tests   # Infrastructure provisioning tests
+cargo run --bin e2e-deployment-workflow-tests         # Configuration, release, and run workflow tests
+cargo run --bin e2e-infrastructure-lifecycle-tests   # Infrastructure provisioning tests
 
 # Keep the test environment after completion for inspection
-cargo run --bin e2e-tests-full -- --keep
-cargo run --bin e2e-provision-and-destroy-tests -- --keep
+cargo run --bin e2e-complete-workflow-tests -- --keep
+cargo run --bin e2e-infrastructure-lifecycle-tests -- --keep
 
 # Use custom templates directory
-cargo run --bin e2e-tests-full -- --templates-dir ./custom/templates
+cargo run --bin e2e-complete-workflow-tests -- --templates-dir ./custom/templates
 
 # See all available options
 cargo run --bin e2e-tests-full -- --help
@@ -190,15 +191,16 @@ cargo run --bin e2e-tests-full -- --help
 
 ### 📖 Manual Deployment Steps
 
-> **✅ Infrastructure commands are now available!** You can create, provision, configure, test, and destroy deployment environments using the CLI.
+> **✅ Complete deployment workflow is now available!** You can create, provision, configure, test, deploy, run, and destroy Torrust Tracker environments using the CLI.
 >
 > **Current Status:**
 >
 > - ✅ **Environment Management**: Create and manage deployment environments
-> - ✅ **Infrastructure Provisioning**: Provision VM infrastructure with LXD
+> - ✅ **Infrastructure Provisioning**: Provision VM infrastructure with LXD or Hetzner Cloud
 > - ✅ **Configuration**: Configure provisioned infrastructure (Docker, Docker Compose)
 > - ✅ **Verification**: Test deployment infrastructure
-> - ⚠️ **Application Deployment**: Not yet available - tracker application deployment coming soon
+> - ✅ **Application Deployment**: Deploy Torrust Tracker configuration and database
+> - ✅ **Service Management**: Start and manage tracker services
 >
 > **Available Commands:**
 >
@@ -220,7 +222,13 @@ cargo run --bin e2e-tests-full -- --help
 > # 6. Verify deployment infrastructure
 > torrust-tracker-deployer test my-environment
 >
-> # 7. Destroy environment when done
+> # 7. Deploy tracker application configuration
+> torrust-tracker-deployer release my-environment
+>
+> # 8. Start tracker services
+> torrust-tracker-deployer run my-environment
+>
+> # 9. Destroy environment when done
 > torrust-tracker-deployer destroy my-environment
 > ```
 >

docker/provisioned-instance/README.md

@@ -176,4 +176,4 @@ This container configuration supports the E2E test split architecture:
 ## Related Documentation
 
 - [Docker Configuration Testing Research](../../docs/research/e2e-docker-config-testing.md)
-- [E2E Testing Guide](../../docs/e2e-testing.md)
+- [E2E Testing Guide](../../docs/e2e-testing/)