Doc system test

Reference pinning

How push turns username/name[:version] references into fixed version ids, with a missing or 0 version meaning the latest at push time.

Meta block front matter of this doc
namespaces
  • durian.cloud/cyanprint/registry
  • durian.cloud/cyanprint/composition
type
algorithm
code
  • sulfone.zinc/App/Modules/Cyan/API/V1/Mappers/TemplateMapper.cs
  • sulfone.zinc/Domain/Service/TemplateService.cs
  • sulfone.zinc/App/Modules/Cyan/Data/Repositories/TemplateRepository.cs

On push, every template, processor, plugin and resolver reference is looked up. Version 0 or none becomes the highest version number at that moment; a missing reference fails the push and lists what was found. The stored link is the version id, so the tree never moves after push. Preset answers (templates) and config plus file globs (resolvers) are stored on the link.

Where it lives

  • sulfone.zinc/App/Modules/Cyan/API/V1/Mappers/TemplateMapper.cs
  • sulfone.zinc/Domain/Service/TemplateService.cs
  • sulfone.zinc/App/Modules/Cyan/Data/Repositories/TemplateRepository.cs

Stub: summary only.