# Validate and reload the Caddy configuration (zero-downtime).
# Copy to /etc/ops-agent/flows/update_caddy_config.yml on the host.
#
# Prerequisites:
#   - The new Caddyfile must already be written to /srv/scrum4me/caddy/Caddyfile
#     (e.g. via the Caddy editor in the Ops Dashboard, or edited by hand).
#
# Steps:
#   1. Validate the Caddyfile syntax (caddy validate)
#   2. Reload Caddy via its admin API — zero-downtime config swap
#   3. Smoke-test public hostnames: curl -I, expect 200/301/308/401
#
# For a hard container restart instead of a graceful reload, use
# update_caddy_config_force.yml (needed after port/TLS listener changes).
#
# Smoke-test commands must be registered in commands.yml.
# Add one curl_smoke_<name> entry per public hostname. Example:
#
#   curl_smoke_scrum4me_web:
#     cmd: ["curl", "-sI", "--max-time", "10", "https://scrum4me.example.com/api/health"]
#     description: "Smoke test scrum4me-web HTTPS endpoint"
#
# Then add one step per hostname below:
#
#   - command_key: curl_smoke_scrum4me_web
#     on_failure: continue
#   - command_key: curl_smoke_other_site
#     on_failure: continue

name: Update Caddy Config
description: Validate the Caddyfile and reload Caddy (zero-downtime via admin API)
steps:
  - command_key: caddy_validate
    on_failure: abort

  - command_key: caddy_reload
    on_failure: abort

  # Add one smoke-test step per public hostname served by Caddy.
  # Accepted exit codes: 0 (200/301/308) or 22 (4xx, use --fail to control).
  # on_failure: continue keeps the flow going even if a hostname is temporarily slow.
  - command_key: curl_smoke_scrum4me_web
    on_failure: continue