From: LightDiscord via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: LightDiscord <root@arnaud.sh>
Subject: [pve-devel] [PATCH proxmox 0/2] Enable upload button for snippets
Date: Wed, 17 Jul 2024 18:22:46 +0000 [thread overview]
Message-ID: <mailman.2.1722093010.302.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 4092 bytes --]
From: LightDiscord <root@arnaud.sh>
To: pve-devel@lists.proxmox.com
Subject: [PATCH proxmox 0/2] Enable upload button for snippets
Date: Wed, 17 Jul 2024 18:22:46 +0000
Message-ID: <20240717182228.27812-2-root@arnaud.sh>
Hi everyone,
I wanted to use cloud-init by only interacting with the Web UI on Proxmox.
In all the steps required to do this, we need to reference snippets when
using the `cicustom` option. However, it's not possible to upload them
through the UI. It's currently only possible to delete them.
The following two patches attempts to enable the upload route on the API
and enable the upload button on the UI. I've tested both of them and it
seems to work with the tests I did (upload and download from URL small yaml
files).
NOTE: Some discussions for this feature had concern about the hookscript
snippets, in this case I'm focusing only on cloud-init snippets so I allowed
only `.yml` and `.yaml` files. Some people were also talking about Ignition
maybe enable all extension in the future ?
Reference:
* https://bugzilla.proxmox.com/show_bug.cgi?id=2208
NOTE: It's the first time I'm using git send-email and trying to contribute
to multiple repositories at the same time. If the subject of the e-mails or
anything else is wrong, don't hesitate to send me a direct e-mail.
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2024-07-27 15:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.2.1722093010.302.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=root@arnaud.sh \
/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