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
docs(readme): document exportToCache field and SLSA L3 usage
Update Docker packages section in README with exportToCache field
documentation and SLSA Level 3 compliance information.
Changes:
- Add exportToCache field to YAML example with inline comments
- Document default behavior (false = legacy push)
- Document export mode (true = cache for signing)
- Note override mechanisms (CLI flag and env var)
- Add SLSA L3 compliance section with usage examples
- Reference to 'leeway build --help' for details
Documentation follows existing README patterns with concise
explanations and practical examples.
Co-authored-by: Ona <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,6 +170,11 @@ config:
170
170
config:
171
171
# Dockerfile is the name of the Dockerfile to build. Automatically added to the package sources.
172
172
dockerfile: "Dockerfile"
173
+
# exportToCache controls whether images are pushed directly or exported to cache
174
+
# - false (default): push directly to registry (legacy behavior)
175
+
# - true: export to cache for signing (enables SLSA L3 compliance)
176
+
# Can be overridden via --docker-export-to-cache flag or LEEWAY_DOCKER_EXPORT_TO_CACHE env var
177
+
exportToCache: false
173
178
# Metadata produces a metadata.yaml file in the resulting package tarball.
174
179
metadata:
175
180
foo: bar
@@ -191,6 +196,12 @@ The name of this build argument is the package name of the dependency, transform
191
196
192
197
E.g. `component/nested:docker` becomes `COMPONENT_NESTED__DOCKER`.
193
198
199
+
**For SLSA Level 3 compliance:** Set `exportToCache: true` to enable cache-based Docker image distribution with cryptographic signing. This can be overridden globally using:
0 commit comments