From: Simon LEONARD <git-1001af4@sinux.sh>
To: pve-devel@lists.proxmox.com
Cc: Simon LEONARD <git-1001af4@sinux.sh>
Subject: [pve-devel] [PATCH container 0/1] close #1543: allow low-level lxc update
Date: Thu, 23 Jan 2025 23:29:46 +0100 [thread overview]
Message-ID: <20250123222951.112660-1-git-1001af4@sinux.sh> (raw)
Hello,
I'm trying to fully automate my homelab with Proxmox and infra as code
with Pulumi.
A missing feature is to allow the modification of low-level lxc settings
via the API, as spotted in #1543. Today, the GET config endpoint returns
the current low-level configuration but don't allow to edit it (PUT).
I've tried to implement this feature, and it works on my instance.
However I'm really new to Proxmox, Perl and git send-email so input
would be appreciated/necessary.
Originally (wrongly) posted in https://forum.proxmox.com/threads/161059/
Simon LEONARD (1):
close #1543: allow low-level lxc config update
src/PVE/API2/LXC/Config.pm | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
--
2.48.1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-01-24 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 22:29 Simon LEONARD [this message]
2025-01-23 22:29 ` [pve-devel] [PATCH container 1/1] " Simon LEONARD
2025-01-27 11:05 ` Fabian Grünbichler
2025-03-22 18:05 ` [pve-devel] [PATCH container v2 0/1] close #1543: allow low-level lxc config Simon LEONARD
2025-03-22 18:05 ` [pve-devel] [PATCH container v2 1/1] close #1543: allow low-level lxc config update Simon LEONARD
2025-03-24 15:01 ` [pve-devel] [PATCH container v2 0/1] close #1543: allow low-level lxc config Fabian Grünbichler
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=20250123222951.112660-1-git-1001af4@sinux.sh \
--to=git-1001af4@sinux.sh \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.