From: Filip Schauer <f.schauer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 1/2] ui: storage: oci registry pull: fix reference parsing
Date: Tue, 18 Nov 2025 17:26:20 +0100 [thread overview]
Message-ID: <20251118162628.180674-2-f.schauer@proxmox.com> (raw)
In-Reply-To: <20251118162628.180674-1-f.schauer@proxmox.com>
Fixes an issue where pasting an OCI image reference with a additional
prefix (for example docker://registry.fedoraproject.org/fedora:latest)
into the reference field caused the tag parser to split the string
incorrectly. With this patch the tag is only moved when a valid OCI
reference is entered.
Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
---
www/manager6/storage/TemplateView.js | 30 +++++++++++++++++++++-------
1 file changed, 23 insertions(+), 7 deletions(-)
diff --git a/www/manager6/storage/TemplateView.js b/www/manager6/storage/TemplateView.js
index d570efb4..6ce6d1f6 100644
--- a/www/manager6/storage/TemplateView.js
+++ b/www/manager6/storage/TemplateView.js
@@ -201,15 +201,31 @@ Ext.define('PVE.storage.OciRegistryPull', {
let view = me.getView();
let tagField = view.down('[name=tag]');
tagField.setComboItems([]);
+ let matches = me.parseReference(value);
+ if (matches) {
+ let ref = matches[0];
+ let tag = matches[1];
+
+ if (tag) {
+ field.setValue(ref);
+ tagField.setValue(tag);
+ tagField.focus();
+ } else {
+ tagField.clearValue();
+ }
+ }
+ },
- let parts = value.split(':');
- if (parts.length > 1) {
- field.setValue(parts[0]);
- tagField.setValue(parts[1]);
- tagField.focus();
- } else {
- tagField.clearValue();
+ parseReference: function (value) {
+ const re =
+ /^((?:(?:[a-zA-Z\d]|[a-zA-Z\d][a-zA-Z\d-]*[a-zA-Z\d])(?:\.(?:[a-zA-Z\d]|[a-zA-Z\d][a-zA-Z\d-]*[a-zA-Z\d]))*(?::\d+)?\/)?[a-z\d]+(?:(?:[._]|__|[-]*)[a-z\d]+)*(?:\/[a-z\d]+(?:(?:[._]|__|[-]*)[a-z\d]+)*)*)(:(\w[\w.-]{0,127}))?$/;
+ let matches = value.match(re);
+ if (matches) {
+ let ref = matches[1];
+ let tag = matches[3];
+ return [ref, tag];
}
+ return undefined;
},
queryTags: function (field) {
--
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 ` Filip Schauer [this message]
2025-11-18 16:26 ` [pve-devel] [PATCH manager 2/2] ui: storage: oci registry pull: add reference validator Filip Schauer
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-2-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 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.