Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
Used in: ,
A registration carrying only this flag (and the path) says the path's keys are named by the user - a values path read whole, such as a list of roles or queries - without making it an object collection the way `subkey` does. The validator reads it.
Settings is an internal message. It is not used to submit checks or query status instead it is used to interact with the settings store. The settings is a central component inside NSClient++ and this is the way to interact with it. message Settings {
Used in: , , , , , ,
Used in:
Used in:
Used in:
Used in:
See Query.redact_sensitive: mask values for sensitive keys.
Used in:
When set, values for keys registered sensitive (add_password / is_sensitive_key) are returned as "***". Opt-in so internal self-reads (modules loading their own secrets) still get the real value; the REST read endpoints set it, nothing else does.
Used in:
Used in:
(message has no fields)
Used in:
An empty `node.value` removes the key (or, with an empty key too, the whole path) - unless `store_empty` is set, in which case the key is set to the empty string. Senders that predate the field keep the remove behaviour.
Compare the saved configuration against what the loaded modules registered (settings_core::validate()).
Used in:
(message has no fields)
Used in:
Used in:
(message has no fields)
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
(message has no fields)
Used in:
Used in:
(message has no fields)
Used in:
Used in:
Mirrors settings::validation_finding::kind.
Used in:
Used in: