pub struct RuntimeConfig {Show 18 fields
pub list_children_batch_size: usize,
pub security_policy: Arc<SecurityPolicy>,
pub debug: bool,
pub enable_introspection: bool,
pub use_builtin_process_launcher: bool,
pub maintain_utc_clock: bool,
pub num_threads: usize,
pub namespace_capabilities: Vec<CapabilityDecl>,
pub builtin_capabilities: Vec<CapabilityDecl>,
pub root_component_url: Option<Url>,
pub component_id_index_path: Option<Utf8PathBuf>,
pub log_destination: LogDestination,
pub log_all_events: bool,
pub builtin_boot_resolver: BuiltinBootResolver,
pub realm_builder_resolver_and_runner: RealmBuilderResolverAndRunner,
pub abi_revision_policy: AbiRevisionPolicy,
pub vmex_source: VmexSource,
pub health_check: HealthCheck,
}
Expand description
Runtime configuration options. This configuration intended to be “global”, in that the same configuration is applied throughout a given running instance of component_manager.
Fields§
§list_children_batch_size: usize
How many children, maximum, are returned by a call to ChildIterator.next()
.
security_policy: Arc<SecurityPolicy>
Security policy configuration.
debug: bool
If true, component manager will be in debug mode. In this mode, component manager
provides the EventSource
protocol and exposes this protocol. The root component
must be manually started using the LifecycleController protocol in the hub.
This is done so that an external component (say an integration test) can subscribe to events before the root component has started.
enable_introspection: bool
Enables Component Manager’s introspection APIs (RealmQuery, RealmExplorer, RouteValidator, LifecycleController, etc.) for use by components.
use_builtin_process_launcher: bool
If true, component_manager will serve an instance of fuchsia.process.Launcher and use this launcher for the built-in ELF component runner. The root component can additionally use and/or offer this service using ‘/builtin/fuchsia.process.Launcher’ from realm.
maintain_utc_clock: bool
If true, component_manager will maintain a UTC kernel clock and vend write handles through
an instance of fuchsia.time.Maintenance
. This flag should only be used with the top-level
component_manager.
num_threads: usize
§namespace_capabilities: Vec<CapabilityDecl>
The list of capabilities offered from component manager’s namespace.
builtin_capabilities: Vec<CapabilityDecl>
The list of capabilities offered from component manager as built-in capabilities.
root_component_url: Option<Url>
URL of the root component to launch. This field is used if no URL is passed to component manager. If value is passed in both places, then an error is raised.
component_id_index_path: Option<Utf8PathBuf>
Path to the component ID index, parsed from
fuchsia.component.internal.RuntimeConfig.component_id_index_path
.
log_destination: LogDestination
Where to log to.
log_all_events: bool
If true, component manager will log all events dispatched in the topology.
builtin_boot_resolver: BuiltinBootResolver
Which builtin resolver to use for the fuchsia-boot scheme. If not supplied this defaults to the NONE option.
realm_builder_resolver_and_runner: RealmBuilderResolverAndRunner
If and how the realm builder resolver and runner are enabled.
abi_revision_policy: AbiRevisionPolicy
The enforcement and validation policy to apply to component target ABI revisions.
vmex_source: VmexSource
Where to get the vmex resource from.
health_check: HealthCheck
Components that opt into health checks before an update is committed.