service-pipeline: action-deployer and action-config disagree on default matrix config path #123

Problem

In service-pipeline.yaml, action-config@v3 (setup job) and action-deployer@v0 (deploy job) default to different matrix config filenames — .github/matrix-config.yaml (hyphen) vs .github/matrix.config.yaml (dot). The workflow's config_path input is only forwarded to action-config, never to action-deployer, so the deploy job always falls back to its hardcoded default.

Context

Consuming repos using the documented matrix-config.yaml name get a green setup but a silently failing deploy: reading config .github/matrix.config.yaml: open .github/matrix.config.yaml: no such file or directory. Images still build/push and the release publishes, but the GitOps tag bump never happens. This left DND-IT/fission's gotthard prod deployment ~12 days stale before detection.

Proposed approach

• Forward the same config path to both jobs, e.g. pass config: ${{ inputs.config_path || '.github/matrix-config.yaml' }} to the action-deployer step.
• Align the two actions' default filenames to remove the discrepancy entirely.

Acceptance criteria

• deploy job in service-pipeline.yaml uses the same config path as setup.
• Default filenames across action-config and action-deployer are consistent (or workflow explicitly reconciles them).
• Add a regression test/check ensuring config path consistency between setup and deploy jobs.