Skip to content

Clarify organization-level configuration and console.viewer #4281

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.

Sign up for GitHub

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

Draft
tylerpaxton wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Clarify organization-level configuration and console.viewer #4281

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8365e59
Clarify organization-level configuration and console.viewer
tylerpaxton Oct 21, 2026
8eedf98
Merge main into tp.checks-org-config-scope
tylerpaxton Oct 22, 2026
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
2 changes: 1 addition & 1 deletion content/chainguard/checks/identity-and-trust.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,7 +141,7 @@ Each host accepts the following roles:
| `libraries.cgr.dev` | `libraries.javascript.pull` | Download JavaScript libraries from Chainguard Libraries. |
| `libraries.cgr.dev` | `libraries.python.pull` | Download Python libraries from Chainguard Libraries. |
| `libraries.cgr.dev` | `libraries.java.pull` | Download Java libraries from Chainguard Libraries. |
| `console-api.enforce.dev` | `console.viewer` | List groups, identities, roles, role bindings, and identity providers in the Chainguard API. |
| `console-api.enforce.dev` | `console.viewer` | List groups, identities, roles, role bindings, and identity providers in the Chainguard API. Unlike the other roles in this table, `console.viewer` isn't the name of an IAM role, so bind the assumable identity to one that grants this access, such as `console_viewer`. |

A check that uses a Chainguard host must list it in `network.egress`, along with any host that the service redirects downloads to.

Expand Down
4 changes: 3 additions & 1 deletion content/chainguard/guardener/github/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ linktitle: "Configuration"
description: "Understand Guardener's .chainguard/ configuration model and how to enable features per repository."
type: "article"
date: 2026-07-08T00:00:00+00:00
lastmod: 2026-10-13T13:59:25+00:00
lastmod: 2026-10-21T00:00:00+00:00
draft: false
tags: ["GitHub", "Configuration"]
images: []
Expand Down Expand Up @@ -75,6 +75,8 @@ To use org-level configuration:

Once in place, every repository Guardener can access inherits this configuration without needing its own `.chainguard/` files.

Organization-level configuration covers only Guardener's files. Chainguard Checks and Chainguard Workspaces never read `ci.yaml`, the `ci/` directory, or `develop.yaml` from the `.github` repository, so commit those files to each repository that uses them.

### How repository and organization configuration combine

Configuration committed directly to a repository takes precedence over the organization-level configuration from the `.github` repository:
Expand Down
Loading