[pve-devel] [RFC pve-common v2 2/2] new schema property addStandardCliParameters
Dietmar Maurer
dietmar at proxmox.com
Tue Jul 24 13:42:07 CEST 2018
OK, I will try to remove all those magic ...
> On July 24, 2018 at 12:16 PM Dietmar Maurer <dietmar at proxmox.com> wrote:
>
>
> > 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?
>
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
More information about the pve-devel
mailing list