Skip to content

stevedore docker-release: support private-modules (BuildKit gh_token secret) for covenant cutover #43

Description

@blairham

The frozen matrix docker-release.yml@pre-stevedore has a private-modules: true input that mints a short-lived pinpredict-argocd App token and mounts it as BuildKit secret id=gh_token, for Dockerfiles that fetch a private pinpredict module (e.g. unvendored github.com/pinpredict/ppkit) — see the action's original design.

The stevedore docker-release.yml on @main (#40) dropped that input. covenant is the one migration-pending repo that uses private-modules: true (ppkit consumer), so it can't cut over until the stevedore workflow restores an equivalent.

Options

  • Add a private-modules boolean input to the stevedore docker-release.yml: when true, run actions/create-github-app-token and export the token to an env var; stevedore's .stevedore.yaml already supports a secrets: block ({id: gh_token, env: GH_TOKEN}) that mounts it as a BuildKit --secret. So the workflow mints + exports, and covenant's config opts in per image. This is the clean path — the secrets plumbing already exists in stevedore (verified in the schema).
  • covenant's .stevedore.yaml (already merged, covenant#48) would add the secrets: entry to its image in the cutover PR.

Until then covenant stays on @pre-stevedore. All other repos cut over without this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    claude-followupFollow-up work captured from a Claude session

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions