Answer A-430a: every wanted build has a version; the node-engine resolves artifacts by version through the registry's versions verb
This commit is contained in:
@@ -1141,3 +1141,11 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
tags it, and the registry's answer is what it applies. §379's digests in the want, and the assigner's check whether
|
||||
a node's node-engine reads them (`want-parts`), go. A build of another watched branch, which has no released
|
||||
version, is named by the version the builder numbered it under.
|
||||
- **A-430a** (A-430; principles 7 and 8) Every build a want names has a version: a released trunk build its released
|
||||
version, a build of another watched branch the version the builder numbered it under (A-430), and a kept build its
|
||||
numbered version with `kept-on` naming the node that keeps it (§526); a want never names a fingerprint's artifacts
|
||||
or digests. The node-engine resolves each artifact the catalog entry names at that version through the seat that
|
||||
holds its kind (`oci-artifact-registry` for a bundle or archive, `container-image-registry` for an image), by its
|
||||
verb `versions` with the artifact's registry name `<module>/<artifact>`, and fetches the bytes as today over the
|
||||
artifact store by the digest that answer gives; an image is pulled by name and version. The node-engine's manifest
|
||||
invokes those `versions` verbs; no registry verb is added.
|
||||
|
||||
Reference in New Issue
Block a user