ai-workspace-services/billing-service
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
3570240c69
billing-service/docs/release-traceability.md
Haitao Pan 73da08f8ae fix release traceability validation target
2026-04-12 17:41:43 +08:00

1.5 KiB
Raw Blame History

Release Traceability Contract

This repository now treats IMAGE as the single runtime source of truth for release identity.

Runtime contract

  • IMAGE must contain the full image reference used to start the container.
  • /api/ping returns image, tag, commit, and version.
  • tag, commit, and version are derived from IMAGE.
  • If IMAGE is missing or malformed, the derived fields stay empty instead of being fabricated.

Pipeline contract

  • Build must produce service_image_ref only from the full GITHUB_SHA.
  • Deploy must consume service_image_ref and pass it through as the runtime image identity.
  • Validate must use GET https://accounts.svc.plus/api/ping.
  • Validate must derive tag and commit from service_image_ref and compare them against /api/ping.
  • Validate must fail when runtime image, tag, commit, or version is empty.
  • Validate must compare version against the derived full commit, not a synthetic fallback.

External playbook alignment

The external playbooks/deploy_billing_service.yml playbook should accept IMAGE_REF (or an equivalent full image reference variable), derive any repo/tag helpers from it, and inject IMAGE=<full image ref> into the running container environment for the service exposed through https://accounts.svc.plus/api/ping.

If accounts.svc.plus/api/ping keeps returning empty runtime metadata, treat that as a deployment contract failure: the runtime did not receive the full IMAGE value and release traceability is broken.