Struct ServiceComponent 

pub struct ServiceComponent {
    pub id: String,
    pub kind: String,
    pub path: String,
    pub git: Option<GitSource>,
    pub role: String,
    pub publishes: Option<String>,
    pub mount: Option<String>,
    pub wave: u32,
    pub deploy: DeployTier,
}

One component of a ServiceConfig. The kind (e.g. "mesofact-static", "almanac", "container") selects which reconciler runs against the pointed-at workload manifest.

Fields

id: String

kind: String

path: String

Path of the directory holding this component’s workload.toml. Relative to the workspace root for in-tree components, or to the materialized <checkout>/<subdir> when git is set.

git: Option<GitSource>

Optional external git source (R561-F1). When set, the component’s code is materialized by shallow-clone before build; see GitSource.

role: String

Operator-facing role label, e.g. "static", "dynamic", "compute".

publishes: Option<String>

Optional artifact kind this component publishes ("static", "container-image", …). Drives mirror provider-slot routing.

mount: Option<String>

URL sub-path a static component’s build output is published under, relative to the service’s publish prefix (R746). None = the service root, which is what every pre-R746 component means.

Static publishers lay a component’s out_dir down at <bucket>/<service>/<env>/… and the front door fetches ${ASSET_ORIGIN}/<request path> — the request path is the key. So a service with two static components had them overwrite each other at one prefix, and there was no way to say “this bundle serves under /app”. mount is that: it appends to the publish prefix, which makes the URL sub-path and the storage sub-path the same string by construction rather than by two manifests agreeing.

Cross-checked against the domain route that names the component (CloudConfig::cross_ref_validate): a component mounted at /app must be routed at /app or /app/*, because a disagreement means requests land on a prefix nothing published to — a 404 whose cause is two files apart.

wave: u32

Sync-wave index (0-based). Components in wave 0 roll out in parallel first; the reconciler waits for all wave-N components to become healthy before starting wave N+1. Defaults to 0 (all components in one wave).

deploy: DeployTier

Whether this component ships inside the service’s one assembled bundle or as a deployed unit of its own (R870-F23).

This is the vocabulary R870-F15’s design needed and the config did not have. [providers.bundle] is a per-mirror slot, so before this there was no way to say “give this one component its own workload” at all — the whole service was one bundle or it was nothing, and a service whose components genuinely release on different cadences had no shape to declare.

It is one field rather than a pair of flags on purpose: a component being both bundle-staged and its own workload is the second admission rule R870-F23 was asked to enforce, and an enum makes it unrepresentable instead of merely refused.

Trait Implementations

impl Clone for ServiceComponent

fn clone(&self) -> ServiceComponent

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ServiceComponent

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ServiceComponent

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for ServiceComponent

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.