[pve-devel] [RFC pve-common v2 2/2] new schema property addStandardCliParameters

[Dietmar Maurer]

> IMO, this is the responsibility of the CLI cmddef, not the API schema
> pointed to from the cmddef. We can have multiple CLI commands pointing 
> to the same API path, with different output transformations for example,
> where on one command it may make sense but on the other not.

I do not really see this use case (examples)?

> That's why I put the workaround to turn this intrusive behavior of 
> inserting - possibly overwriting - CLI commands options off in options 
> not in the schema.

Your workaround does not work, because you cannot set 
$options->{'std-output-opts'}. Maybe I miss how to use that?