From 8365e59a7d9063edff27ffd03985bc40c669401d Mon Sep 17 00:00:00 2001 From: Tyler Paxton Date: Wed, 21 Oct 2026 09:01:55 -0700 Subject: [PATCH] Clarify organization-level configuration and console.viewer Guardener's configuration page lists the Chainguard Checks and Chainguard Workspaces files right before its organization-level section, so they read as if the .github repository can supply them. Neither product reads them from there, so say so on that page. On the identities page, say that console.viewer isn't an IAM role name, and which built-in role to bind the assumable identity to. Co-Authored-By: Claude Opus 5.5 --- content/chainguard/checks/identity-and-trust.md | 4 ++-- content/chainguard/guardener/github/configuration.md | 4 +++- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/content/chainguard/checks/identity-and-trust.md b/content/chainguard/checks/identity-and-trust.md index e766e2cabd..239c24e7f0 100644 --- a/content/chainguard/checks/identity-and-trust.md +++ b/content/chainguard/checks/identity-and-trust.md @@ -4,7 +4,7 @@ linktitle: "Identities and trust" description: "Learn how a Chainguard Checks check gets short-lived Google Cloud or Chainguard credentials through a workload identity, how to limit which pull requests get one, and how to revoke access." type: "article" date: 2026-10-12T00:00:00+00:00 -lastmod: 2026-10-20T18:30:00+00:00 +lastmod: 2026-10-21T00:00:00+00:00 draft: false tags: ["Chainguard Checks", "Configuration", "Security"] images: [] @@ -137,7 +137,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. diff --git a/content/chainguard/guardener/github/configuration.md b/content/chainguard/guardener/github/configuration.md index 7ebd3f623d..eb725ca9e0 100644 --- a/content/chainguard/guardener/github/configuration.md +++ b/content/chainguard/guardener/github/configuration.md @@ -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: [] @@ -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: