pub struct FeaturesConfig {
pub didcomm: bool,
pub tsp: bool,
pub rest_api: bool,
pub agent_names: bool,
pub deployment_mode: String,
}Fields§
§didcomm: bool§tsp: boolTrust Spanning Protocol (TSP) transport. When enabled (and a
mediator_did is configured), the mediator listener also carries
TSP on its shared socket and the service’s DID document advertises
a TSPTransport service. Additive with didcomm — a node can
speak both; TSP is preferred when a peer advertises both.
rest_api: bool§agent_names: boolServe agent-name redirects (GET /@alice -> 302 to a DID).
On by default. A name only resolves if the signed DID document
already claims it via alsoKnownAs, so serving the /@… namespace
cannot by itself expose a name the controller has not authorised: with
no names bound, every /@… request 404s exactly as it did before.
Meanwhile the write path (bind/park/resume, over REST and Trust Tasks)
and the UI that drives it are not gated on this flag — leaving it off
let an owner bind a name that then silently failed to resolve, which is
the worse default.
Set agent_names = false (or …_FEATURES_AGENT_NAMES=0) to keep the
/@… namespace unserved on a host that wants those paths free for
something else.
deployment_mode: StringDeployment mode: “standalone” for individual services, “daemon” for unified binary. Controls UI behavior (e.g., hiding service topology in daemon mode).
Trait Implementations§
Source§impl Clone for FeaturesConfig
impl Clone for FeaturesConfig
Source§fn clone(&self) -> FeaturesConfig
fn clone(&self) -> FeaturesConfig
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Debug for FeaturesConfig
impl Debug for FeaturesConfig
Source§impl Default for FeaturesConfig
Hand-written so the in-code default matches what serde fills in for an
absent field — a derived Default would give agent_names: false and an
empty deployment_mode, so every ..Default::default() call site (the
setup wizards, the recipe writer, tests) would disagree with the same
config round-tripped through TOML.
impl Default for FeaturesConfig
Hand-written so the in-code default matches what serde fills in for an
absent field — a derived Default would give agent_names: false and an
empty deployment_mode, so every ..Default::default() call site (the
setup wizards, the recipe writer, tests) would disagree with the same
config round-tripped through TOML.