From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH storage] volume import: assume target API version is at least 9
Date: Fri, 5 Jul 2024 09:45:09 +0200 [thread overview]
Message-ID: <11ecd280-d911-4c32-a77d-1bd27d8c42e0@proxmox.com> (raw)
In-Reply-To: <e8067cbb-0b36-442f-966f-f1c754a8e5d7@proxmox.com>
Am 04/07/2024 um 14:11 schrieb Fiona Ebner:
> Yes, next time we introduce an apiinfo call, we can just have it fail
> hard upon errors.
Oh, and just to avoid potential future error potential here:
For a new topic-specific API version call that might not work, as the fallback
and (lacking) error handling here was added explicitly for backward
<compatibility.
Also, for a future topic-API version info call a new central API endpoint
would be preferable. That we could more easily expand for various different
internal API versioning and have central tooling to query it correctly,
which would be simpler too as one can nicely differentiate auth/network/..
errors from an actual application level one, like 404 not found.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-07-05 7:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 9:04 Fiona Ebner
2024-07-02 17:14 ` Max Carrara
2024-07-03 12:26 ` [pve-devel] applied: " Fiona Ebner
2024-07-04 9:52 ` [pve-devel] " Thomas Lamprecht
2024-07-04 10:28 ` Fiona Ebner
2024-07-04 11:51 ` Thomas Lamprecht
2024-07-04 12:11 ` Fiona Ebner
2024-07-04 17:45 ` Thomas Lamprecht
2024-07-05 8:22 ` Fiona Ebner
2024-07-25 12:38 ` Thomas Lamprecht
2024-07-05 7:45 ` 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=11ecd280-d911-4c32-a77d-1bd27d8c42e0@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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