From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dylan Whyte <d.whyte@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-access-control] resource pools: add resource pool cli commands
Date: Thu, 28 Jan 2021 14:19:44 +0100 [thread overview]
Message-ID: <e8d22f99-ff12-51a3-2361-e4f12d00a7c8@proxmox.com> (raw)
In-Reply-To: <20210128110108.28497-1-d.whyte@proxmox.com>
On 28.01.21 12:01, Dylan Whyte wrote:
> Add commands for creating, modifying, listing, and deleting resource
> pools.
>
> Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
> ---
> PVE/CLI/pveum.pm | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/PVE/CLI/pveum.pm b/PVE/CLI/pveum.pm
> index c98ddde..0540b85 100755
> --- a/PVE/CLI/pveum.pm
> +++ b/PVE/CLI/pveum.pm
> @@ -10,6 +10,7 @@ use PVE::API2::Group;
> use PVE::API2::Role;
> use PVE::API2::ACL;
> use PVE::API2::AccessControl;
> +use PVE::API2::Pool;
> use PVE::API2::Domains;
> use PVE::CLIFormatter;
> use PVE::CLIHandler;
> @@ -145,7 +146,12 @@ our $cmddef = {
> delete => [ 'PVE::API2::ACL', 'update_acl', ['path'], { delete => 1 }],
> list => [ 'PVE::API2::ACL', 'read_acl', [], {}, $print_api_result, $PVE::RESTHandler::standard_output_options],
> },
> -
> + pool => {
> + add => [ 'PVE::API2::Pool', 'create_pool', ['poolid'] ],
> + modify => [ 'PVE::API2::Pool', 'update_pool', ['poolid'] ],
> + delete => [ 'PVE::API2::Pool', 'delete_pool', ['poolid'] ],
> + list => [ 'PVE::API2::Pool', 'index', [], {}, $print_api_result, $PVE::RESTHandler::standard_output_options],
> + },
> realm => {
> add => [ 'PVE::API2::Domains', 'create', ['realm'] ],
> modify => [ 'PVE::API2::Domains', 'update', ['realm'] ],
> @@ -176,6 +182,10 @@ our $cmddef = {
>
> aclmod => { alias => 'acl modify' },
> acldel => { alias => 'acl delete' },
> +
> + pooladd => { alias => 'pool add' },
> + poolmod => { alias => 'pool modify' },
> + pooldel => { alias => 'pool delete' },
Those aliases are only for backward compatibility for the old version, from
when we introduced sub-commands. New commands do not need them as we prefer
sub-commands.
> };
>
> 1;
>
prev parent reply other threads:[~2021-01-28 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 11:01 Dylan Whyte
2021-01-28 11:01 ` [pve-devel] [PATCH pve-docs] resource-pools: add section in docs Dylan Whyte
2021-01-28 13:19 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e8d22f99-ff12-51a3-2361-e4f12d00a7c8@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.whyte@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox