Skip to content

Configure additional certificate extensions for Buildkite #1903

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 16, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion config/identity/config.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -236,4 +236,13 @@ ci-issuer-metadata:
*buildkite-type:
default-template-values:
url: "https://buildkite.com"
subject-alternative-name-template: "{{.url}}/{{.organization_slug}}/{{.pipeline_slug}}"
extension-templates:
# Link to the specific Buildkite job that the OIDC token was generated from
run-invocation-uri: "{{.url}}/{{.organization_slug}}/{{.pipeline_slug}}/builds/{{.build_number}}#{{.job_id}}"
# Was the job executed on Buildkite operated compute or customer hosted compute? (valid values: self-hosted, buildkite-hosted)
runner-environment: "runner_environment"
# The git sha that job was running, available in the `build_commit` claim
source-repository-digest: "build_commit"
# build_source: Event that triggered this workflow run. (valid values: api, ui, webhook, trigger_job, schedule)
build-trigger: "build_source"
subject-alternative-name-template: "{{.url}}/{{.organization_slug}}/{{.pipeline_slug}}" # seems correct, do we still need the code in pkg/identity/buildkite/principal.go ?
Loading
Loading