Skip to content

build(mock): release the mock server image #592

Open

Description

@uniqueg

Why

The mock server is deployed on its own, so it needs an image and a release
that is independent of the component releases.

What to do

  • apps/mock-server/Dockerfile: multi-stage, small Node base image,
    runs as non-root and with an arbitrary UID (OpenShift), EXPOSE 8080,
    health check on /healthz. Build context and .dockerignore exclude
    .env* (except .env.example) and all other secret files; no secrets as
    build arguments. Check the root .dockerignore allow list still fits.
  • CI: an image build (and container smoke test against /healthz) job in
    ci.yml, added to the needs: of CI passed.
  • Release workflow release-mock-server.yml / Release mock server on
    tags mock-server-v<version>, following the org pattern used by
    cloud-registry: checks of the tag (signed, on dev), version and CI
    status (prepare), push by digest, scan with
    elixir-cloud-aai/.github/actions/scan-image, then tag, sign/attest and
    create a prerelease GitHub release with curated plus generated notes via
    the shared publish-release action. Job names unique across workflows.
    Confirm release.yml's v* filter does not fire on these tags.
  • Docs: release steps for the mock server in the Contributing page.

Done when

  • Image builds in CI and passes the smoke test; CI passed needs the job
  • A fork dry run on a test tag pushes, scans and creates a release
  • Docs describe the release

Metadata

Metadata

Assignees

Labels

priority: lowLow prioritystatus: blockedSomething prevents progresstype: ci / cdRelated to continuous integration / deliveryworkload: hoursLikely takes hours to resolve

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions