Skip to main content

RECEIPT

tatara_process::annotations

Constant RECEIPT 

Source 
pub const RECEIPT: &str = "tatara.pleme.io/receipt";
Expand description

Label key stamped on every receipt [ConfigMap] that carries a typed crate::receipt::ReceiptEnvelope payload, so operators can kubectl get cm -l tatara.pleme.io/receipt=tatara-receipt/v1 to enumerate every receipt of a given version on a cluster without pre-parsing each CM’s embedded JSON/YAML.

Value is crate::receipt::RECEIPT_VERSION — the wire-format version string every parser gates on. A future bump to tatara-receipt/v2 lands at ONE const declaration on crate::receipt::RECEIPT_VERSION and every consumer that stamps this label picks up the upgrade mechanically.

Load-bearing at TWO production write-sites past the ★★ PRIME-DIRECTIVE ≥ 2 duplication threshold:

  • tatara-closed-loop-probe::write_receipt_cm’s BTreeMap::from([...]) label seed — the closed-loop auth probe’s receipt-CM label writer.
  • tatara_process::configmap::with_data’s byte-shape parity witness test that mirrors the closed-loop-probe callsite.

The tatara-export-worker receipt-CM writer intentionally stamps NO labels (its consumer keys on the CM name the ExportSpec channel already carries), so it is not a consumer of this const; the two production label-stamp sites above are the complete workspace consumer set today.

Peer to ROLE + EXPORT_INDEX on the “annotation / label key stamped on a receipt-emitting resource other than the Process itself” axis-family: those two keys ride on the export-worker Job the reconciler emits (Job-side), this key rides on the receipt ConfigMap the probe binary writes (ConfigMap-side); all three share the GROUP_PREFIX reverse-DNS namespace. A future rename of this key (a tatara.pleme.io/v2/receipt migration, a per-fleet override, a collapse into a compound tatara.pleme.io/receipt-envelope key) lands at ONE pub const in the substrate and every downstream consumer inherits the upgrade mechanically.