om node compliance fix

Run compliance fixes.

--attach

Attach the modulesets specified in a compliance run.

--color=<string>

Colorize output. Possible values are:

• auto: guess based on tty presence
• always|yes: always colorize
• never|no: never colorize

--debug

Increase stream log verbosity up to the debug level.

--filter=<string>

A JSONPath expression to filter a JSON output.

--force

Force action, ignore sanity checks.

--format=<string>

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.

--local

Set to disable cluster-wide operations.

--module=<string>

Specify the modules to limit the run to. The modules must be in already attached modulesets.

--moduleset=<string>

Specify the modulesets to limit the action to. The special value all can be used in conjonction with detach.

--node=<string>

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.

--ruleset-date=<string>

Use an historical ruleset, specified by its date.

--server=<string>

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://1.2.3.4:1214, https://relay.opensvc.com, /var/lib/opensvc/lsnr/h2.sock.

-h, --help

Show this help message and exit