Specification
bucker.yml 2
Bucker configuration as code, version 2. Applying a file is config.apply and each block is applied through its own governed family; this document describes the shape only.
The document
https://spec.bucker.io/bucker-yml/2/schema.json — served as application/schema+json, byte-for-byte the file the repository generates, so what validates here is what the code produces.
curl -s https://spec.bucker.io/bucker-yml/2/schema.json| Specification identifier | https://spec.bucker.io/bucker-yml/2 |
|---|---|
| JSON Schema dialect | https://json-schema.org/draft/2020-12/schema |
| Root type | object |
| Required at the root | version |
| Named subschemas | 0 |
| Size | 297,371 bytes |
Where this identifier appears
The JSON Schema of the bucker.yml configuration-as-code file, version 2, generated from the config kinds registered on the deployment. It describes the shape only; applying a file is still governed per block.
This URL will not move
A change that would alter what an existing document means gets a new version and a new URL. This one keeps resolving, because somebody has already written it into a pipeline that checks bundles without asking us anything. Every published identifier is listed on the specification index, and the namespace itself — https://spec.bucker.io — is never used for anything a reader is expected to fetch other than these documents.