Doc system test

Run-time name lookup

How the coordinator turns a processor or plugin name in a Cyan into a version id, staying inside the template's declared versions.

Meta block front matter of this doc
namespaces
  • durian.cloud/cyanprint/registry
  • durian.cloud/cyanprint/coordinator
type
algorithm
code
  • sulfone.boron/docker_executor/registry.go
  • sulfone.boron/docker_executor/merger.go

A Cyan names processors and plugins as username/name[:version]. With a version, that release is fetched; processors are checked against the template's declared list. Without one, the coordinator asks for the latest and walks back until it finds a version the template declared. Plugins with an explicit version are not checked against the list.

Where it lives

  • sulfone.boron/docker_executor/registry.go
  • sulfone.boron/docker_executor/merger.go

Stub: summary only.