Skip to content

1.0.0

Choose a tag to compare

@neilime neilime released this 04 Nov 18:11
89e3bf9

Features

  • Create disposable VMs with one vm/create action: choose Lima for provisioned cloud images or direct QEMU for unattended installer ISOs and QCOW2 images. Both backends expose the same VM and SSH references.
  • Verify guest state with Goss through vm/test. The action downloads the checksum-pinned verifier, renders suites and variables, uses fresh SSH logins, and publishes native JUnit, summaries, annotations, PR comments and artifacts, including after assertion failures.
  • Run native Ansible Molecule scenarios through ansible/test-molecule. Scenarios own their inventory, target environment and deployment, idempotence, verification and reboot sequence; a VM is optional.
  • Preserve workflow-owned VM lifetime, startup rollback, bounded execution, failure reporting and verified cleanup. Empty assertion suites fail.

Breaking changes and upgrading from 0.2.0

  • Replace vm/test.command or test-script with the required checkout-relative goss-file, plus optional goss-vars. Move provisioning into dedicated workflow steps or Molecule scenarios. Test commands inside Goss remain available for consumer-owned assertions.
  • Remove vm/test.report-file, coverage, path-mapping and github-token. The action publishes its native Goss test reports automatically, uses github.token for eligible PR comments and no longer uploads application coverage to Codecov.
  • Configure Ansible inventory and collection search paths through ansible-config instead of the removed ansible/test.inventory and collections-path inputs. Remove its github-token input.
  • Remove references to outputs from vm/test and ansible/test, vm/create.id, and vm/destroy.removed. Test actions publish reports directly. Creation retains vm and name and adds ssh-config for provisioning and Molecule.
  • Keep vm-config explicit. Use all VM actions in the same job and always schedule destruction, including after test failures. Use ephemeral Linux x86-64 runners with KVM and enough disk and memory for the configured guest.

Usage

Pin related actions to 89e3bf93adc94b592188e714f61d4abc391aab46 (1.0.0). After checkout:

- name: Create VM
  id: vm
  uses: hoverkraft-tech/ci-github-iac/actions/vm/create@89e3bf93adc94b592188e714f61d4abc391aab46 # 1.0.0
  with:
    vm-config: tests/lima.yml
- name: Verify VM
  uses: hoverkraft-tech/ci-github-iac/actions/vm/test@89e3bf93adc94b592188e714f61d4abc391aab46 # 1.0.0
  with:
    vm: ${{ steps.vm.outputs.vm }}
    goss-file: tests/goss.yaml
- name: Destroy VM
  if: ${{ always() && steps.vm.outputs.vm != '' }}
  uses: hoverkraft-tech/ci-github-iac/actions/vm/destroy@89e3bf93adc94b592188e714f61d4abc391aab46 # 1.0.0
  with:
    vm: ${{ steps.vm.outputs.vm }}

Grant contents: read for checkout and pull-requests: write for PR comments. See the VM creation reference, Goss reference, and Molecule reference.

Validation

Merged-main CI passed: 43 unit tests, lint/security checks, Lima and QEMU lifecycle scenarios, fresh SSH group membership, successful/failed/empty/timed-out Goss suites, native reports, Ansible playbook/collection checks and Molecule deployment, idempotence, reboot and cleanup.

Full changelog: 0.2.0...1.0.0