From: Filip Schauer <f.schauer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 2/2] ui: storage: oci registry pull: add reference validator
Date: Tue, 18 Nov 2025 17:26:21 +0100 [thread overview]
Message-ID: <20251118162628.180674-3-f.schauer@proxmox.com> (raw)
In-Reply-To: <20251118162628.180674-1-f.schauer@proxmox.com>
Require a valid OCI reference before allowing submission.
Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
---
www/manager6/storage/TemplateView.js | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/www/manager6/storage/TemplateView.js b/www/manager6/storage/TemplateView.js
index 6ce6d1f6..77418d6c 100644
--- a/www/manager6/storage/TemplateView.js
+++ b/www/manager6/storage/TemplateView.js
@@ -281,6 +281,14 @@ Ext.define('PVE.storage.OciRegistryPull', {
listeners: {
change: 'onReferenceChange',
},
+ validator: function (value) {
+ let me = this;
+ let controller = me.up('pveOciRegistryPull').getController();
+ if (controller.parseReference(value)) {
+ return true;
+ }
+ return gettext('Invalid OCI Registry Reference');
+ },
},
{
xtype: 'button',
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-11-18 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 16:26 [pve-devel] [PATCH manager 0/2] ui: storage: oci registry pull: fix reference validation/parsing Filip Schauer
2025-11-18 16:26 ` [pve-devel] [PATCH manager 1/2] ui: storage: oci registry pull: fix reference parsing Filip Schauer
2025-11-18 16:26 ` Filip Schauer [this message]
2025-11-18 18:32 ` [pve-devel] applied: [PATCH manager 0/2] ui: storage: oci registry pull: fix reference validation/parsing Thomas Lamprecht
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=20251118162628.180674-3-f.schauer@proxmox.com \
--to=f.schauer@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