[akandic47]

Problem

The staging deploy has been failing on the Rendered docker-compose is invalid check added in #206 (e.g. run 33368743093). The rendered compose file is actually valid — the check itself could never succeed because the self-hosted runner is a container without docker, so docker compose config fails for environmental reasons, and the step suppressed all output, making it look like a compose problem.

Change

Replace the docker compose config check with a plain YAML parse using yq:

- name: Validate rendered docker-compose
  run: yq . docker-compose.rendered.yml > /dev/null

This catches the realistic failure mode (envsubst producing broken YAML from a secret value) and prints the parse error with line/column to the log on failure, while discarding stdout so the rendered file's secret values are never echoed. Full compose-schema validation still effectively happens at deploy time via the Portainer HTTP status check from #206.

Requires

yq in the actions-runner image:

sudo apt-get update && sudo apt-get install -y curl jq git gettext yq

On the ghcr.io/actions/actions-runner base (Ubuntu 24.04, python3 preinstalled) this adds only python3-yaml python3-argcomplete python3-toml python3-xmltodict yq.

Verification

Tested in a clean ubuntu:24.04 container against renders of deploy/docker-compose.staging.yml (with dummy secret values):

• valid render → exit 0, no output
• render broken by a multiline secret → exit 1, could not find expected ':' in ..., line 19, column 6

[github-actions]

Go Test coverage is 36.5 %\ ✨ ✨ ✨

[github-actions]

Go Test coverage is 36.5 %\ ✨ ✨ ✨