You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Record where a deploy came from: the commit, the CI run and the trust policy #3061
A deploy's record says who ran it (user) and what it carried. A package or by-reference deploy records package_identifier, and a payload deploy records payload_hash.
Once create-harper's workflow lands (HarperFast/create-harper#144), the most common deploy will be a payload deploy from CI. Its record holds only a hash and the CI user's name. Nothing records the commit, the repository, the workflow run, or that the run authenticated through an OIDC trust policy. The install fingerprint (5.3.1) has no source for a payload either.
The OIDC exchange in security/authn/oidc/tokenExchange.ts verifies all of that: it has the matched policy and GitHub's claims (repository, sha, ref, workflow_ref, run_id, actor, environment). It logs the principal, then mints an operation token that carries only the username, super_user and the operation scope (createOperationToken). By the time deploy_component runs, the provenance is gone.
Proposal
Attested, from the exchange.
Embed the policy id and a fixed set of verified claims in the operation token the exchange mints. Harper signs the token, so the caller can't change them.
deploy_component copies them into the record as source: { via: 'oidc', policy, repository, sha, ref, workflow_ref, run_id, run_attempt, actor, environment }.
Declared, from the CLI. For a deploy that doesn't come through OIDC, the CLI attaches what it knows:
under GitHub Actions, the same GITHUB_* values;
from a local checkout, the commit and whether the tree was dirty.
It's recorded as source: { via: 'declared', … }, so a reader can tell attested provenance from self-reported.
Returned and filterable.get_deployment and list_deployments return source, and list_deployments can filter by sha.
#3048 records { repository, pr, branch, sha } for previews in the provenance file. Use one shape for both.
Done when
A payload deploy from a GitHub Actions run authenticated by OIDC records the repository, commit, run and policy.
A deploy from a laptop records the commit and a dirty flag, marked as declared.
Activity