pub const GROUP_PREFIX: &str = "tatara.pleme.io/";Expand description
Reverse-DNS group prefix — the <GROUP>/ byte-shape every
tatara-owned tatara.pleme.io/* wire-form key (annotation,
finalizer, label, signal) rides through, and the string every
downstream .starts_with(...) group-membership filter compares
against.
Peer to GROUP + VERSION + API_VERSION on the CRD-
group×version axis: where GROUP owns the bare reverse-DNS
segment ("tatara.pleme.io"), VERSION owns the version
segment, and API_VERSION owns the two-segment compose product
("tatara.pleme.io/v1alpha1"), this const owns the ONE-segment
<GROUP>/ product every tatara wire-form key uses as its
namespace prefix ("tatara.pleme.io/"). Pre-lift the prefix was
spelled inline as a bare "tatara.pleme.io/" literal at TWO
substrate-owner sites — annotations::GROUP_PREFIX +
finalizers::GROUP_PREFIX — pinned equal to each other by
[annotations_family_tests::group_prefix_matches_finalizers_group_prefix]
but with no shared owner binding them to GROUP itself. A
future rename that shifted the group segment (a
"tatara.pleme.io/v2/" migration under a group-segment bump, a
per-fleet override, an alias table) would silently unbind the two
peer families from the CRD GROUP itself unless every one of
the three inline literals was updated coherently.
Post-lift the prefix lives at ONE substrate owner here; both
annotations::GROUP_PREFIX and finalizers::GROUP_PREFIX
route through this const as compile-time aliases
(pub const GROUP_PREFIX: &str = crate::GROUP_PREFIX;), so a
rename of the reverse-DNS root lands at ONE pub const here + at
GROUP with the byte-shape pin
[owner_reference_tests::group_prefix_const_composes_group_slash_bytewise]
binding the two consts, rather than at three independent per-
module string literals whose coherence relied on convention.
Byte-shape pinned against format!("{GROUP}/") by
[owner_reference_tests::group_prefix_const_composes_group_slash_bytewise]
(sibling to api_version_const_composes_group_and_version_bytewise
on the same GROUP-composition axis) so a rename of GROUP that
missed this const surfaces HERE rather than as silent skew between
GROUP (which the api_url_prefix composer feeds) and every
downstream <key>.starts_with(GROUP_PREFIX) gate on the peer
annotations::ALL / finalizers::ALL families.