fix: resolve GitHub Actions workflow failure in LXD provisioning test

- Create static cloud-init.yml fixture without template variables
- Update workflow to use static fixture instead of dynamic template
- Add comprehensive workflow documentation explaining purpose and scope
- Fix OpenTofu validation error caused by missing cloud-init.yml file

The workflow now uses fixtures/tofu/lxd/cloud-init.yml as a static
configuration for testing LXD container provisioning in CI environments.
This avoids coupling with application-specific template variables while
maintaining infrastructure validation coverage.

Author: josecelano

.github/workflows/test-lxd-provision.yml

@@ -1,3 +1,22 @@
+# LXD Container Provisioning Test Workflow
+#
+# This workflow tests that LXD container provisioning works correctly in GitHub Actions runners.
+# It's a continuous integration test to ensure our OpenTofu LXD provider configuration is valid
+# and can successfully create containers in shared CI environments.
+#
+# PURPOSE:
+# - Validates OpenTofu configuration syntax and LXD provider integration
+# - Tests container creation, initialization, and basic functionality
+# - Ensures cloud-init scripts work properly in containerized environments
+# - Provides confidence that LXD provisioning works in CI/CD pipelines
+#
+# SCOPE:
+# - Uses static configuration fixtures (no dynamic templating) to avoid application coupling
+# - Tests infrastructure provisioning only (no application deployment)
+# - Focuses on LXD container lifecycle management and basic system validation
+#
+# This is NOT a full end-to-end test but a focused infrastructure validation workflow.
+
 name: Test LXD Container Provisioning
 
 # NOTE: This workflow uses CI-specific approaches like 'sudo chmod 666' on the LXD socket
@@ -45,9 +64,11 @@ jobs:
         run: |
           # Build the template system and render the static templates
           cargo build --release
-          # For this workflow, we need static templates only (no runtime variables)
+          # For this workflow, we use static fixtures without variables for testing
           mkdir -p build
           cp -r templates/* build/
+          # Override the dynamic cloud-init template with static fixture
+          cp fixtures/tofu/lxd/cloud-init.yml build/tofu/lxd/cloud-init.yml
 
       - name: Verify installations
         run: |

fixtures/tofu/lxd/cloud-init.yml

@@ -0,0 +1,26 @@
+#cloud-config
+# Static cloud-init configuration for LXD provisioning tests
+# This is used by GitHub Actions workflow to test LXD container provisioning
+# No SSH keys needed as we don't connect via SSH in the test workflow
+
+# Commented out for faster container creation during CI testing
+# package_update: true
+# package_upgrade: true
+
+# packages:
+#   - curl
+#   - wget
+#   - git
+#   - htop
+#   - vim
+
+users:
+  - name: torrust
+    groups: sudo
+    shell: /bin/bash
+    sudo: ["ALL=(ALL) NOPASSWD:ALL"]
+
+runcmd:
+  - echo "Container provisioned successfully" > /tmp/provision_complete
+  - systemctl enable ssh
+  - systemctl start ssh