om node pushasset¶
Push asset information to collector.
Colorize output. Possible values are:
auto: guess based on tty presence
always|yes: always colorize
never|no: never colorize
If set, the action is actually executed impersonating the scheduler thread.
Increase stream log verbosity up to the debug level.
A JSONPath expression to filter a JSON output.
Specify a data formatter. Possible values are json, flat_json, csv or table. csv and table formatters are available only for commands returning tabular data.
Set to disable cluster-wide operations.
A node selector expression. Embedded in requests for the daemon to route and multiplex the request to a list of nodes. If not specified the local node is targeted.
The server uri to send a request to. If not specified the local node is targeted. Supported schemes are https and raw. The default scheme is https. The default port is 1214 for the raw scheme, and 1215 for https. The uri can be a fullpath to a listener socket. In this case, the scheme is deduced from the socket. Examples: raw://22.214.171.124:1214, https://relay.opensvc.com, /var/lib/opensvc/lsnr/h2.sock.
Use synchronous collector communication. For example, om node pushasset –sync before a compliance run makes sure the pushed data has hit the collector database before the rulesets are contextualized.
Show this help message and exit