pub struct Effective {
pub managed: bool,
pub configuration_suppressed: bool,
pub confirm_each_write_back: bool,
pub notify: Notify,
pub uncomparable_entries: Vec<String>,
/* private fields */
}Expand description
The resolved answer, for an interface that wants to describe it.
The launch path calls decide and does not hold one of these. See the
module note on caching.
Fields§
§managed: boolWhether a policy layer set anything, so the interface can say that settings are administered.
Set something, rather than merely be there. The Linux package ships
/etc/slipcase/open.toml documenting every key and setting none of
them, so a rule that counted the file’s presence would have every
machine that installed the package told its settings were administered
when nothing had been administered — which is the support load concept
10 wants this to reduce, arriving by the front door.
configuration_suppressed: boolWhether the user’s own configuration was suppressed by policy.
confirm_each_write_back: bool§notify: NotifySee Notify.
Read once and held, unlike the lists. The note at the top of this module is about what may be opened, where a value cached across a policy push is a bypass. This one governs how loud the tool is and gates no decision, so nothing is lost by resolving it when the instance starts.
uncomparable_entries: Vec<String>List entries that can never match anything, because they are not comparable under concept 5.2. Surfaced rather than dropped: an entry an administrator wrote and this will never honour is worth a word, and silently ignoring one on a deny list is the worse half.