Skip to main content

component_workload_ident

Function component_workload_ident 

Source
pub fn component_workload_ident(service: &str, component_id: &str) -> String
Expand description

The mesh identity a DeployTier::Workload component registers its service record under.

This is the naming rule, not a lookup, and it is stated here because nothing else states it. A bundle’s ident comes from the mirror (BundleSlot::workload_name, overridable by name = "…"), but a workload-tier component has no slot of its own — [providers.*] is per-kind, per-mirror, which is exactly the gap DeployTier was added to close. So the ident has to be derivable from the two names the service already declares, and this is that derivation.

Getting it wrong is a loud failure rather than a quiet one: InnerDoorPlan::routes_file refuses a mount whose unit resolved to no address, naming the unit, so a component that registered under some other ident fails the apply instead of falling through to the root mount.