From: "Daniel Kral" <d.kral@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager 2/2] ui: use SafeDestroyResource window for removing resources
Date: Tue, 23 Sep 2025 09:50:38 +0200 [thread overview]
Message-ID: <DD00KSC99GK3.3VQ3Z9BA0TS0D@proxmox.com> (raw)
In-Reply-To: <20250917115316.131793-7-m.koeppl@proxmox.com>
On Wed Sep 17, 2025 at 1:53 PM CEST, Michael Köppl wrote:
> This allows users to additionally choose whether they want to purge
> referenced rules that only include the resource that is to be deleted.
>
> Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
> ---
> www/manager6/ha/Resources.js | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/www/manager6/ha/Resources.js b/www/manager6/ha/Resources.js
> index 65897bed2..8bac671d5 100644
> --- a/www/manager6/ha/Resources.js
> +++ b/www/manager6/ha/Resources.js
> @@ -74,12 +74,21 @@ Ext.define('PVE.ha.ResourcesView', {
> handler: run_editor,
> },
> {
> - xtype: 'proxmoxStdRemoveButton',
> + xtype: 'proxmoxButton',
> + text: gettext('Remove'),
With the change from 'proxmoxStdRemoveButton' to 'proxmoxButton' this
should have a `disabled: true`, otherwise it will be enabled even though
the user hasn't select any HA resource.
> selModel: sm,
> - getUrl: function (rec) {
> - return `/cluster/ha/resources/${rec.get('sid')}`;
> + itemId: 'removeBtn',
> + handler: function (btn, e, rec) {
> + Ext.create('PVE.window.SafeDestroyResource', {
> + url: `/cluster/ha/resources/${rec.data.sid}`,
> + item: {
> + id: rec.data.sid,
> + formattedIdentifier: rec.data.sid,
> + },
> + taskName: 'Remove resource',
> + apiCallDone: () => me.rstore.load(),
> + }).show();
> },
> - callback: () => me.rstore.load(),
> },
> ],
> columns: [
_______________________________________________
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-09-23 7:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 11:53 [pve-devel] [PATCH container/docs/ha-manager/manager/qemu-server 0/7] fix #6613: update HA rules upon resource deletion Michael Köppl
2025-09-17 11:53 ` [pve-devel] [PATCH ha-manager 1/2] fix #6613: update rules containing the resource to be deleted Michael Köppl
2025-09-23 7:53 ` Daniel Kral
2025-09-23 8:06 ` Michael Köppl
2025-09-17 11:53 ` [pve-devel] [PATCH ha-manager 2/2] api: add purge parameter for resource deletion Michael Köppl
2025-09-23 7:51 ` Daniel Kral
2025-09-17 11:53 ` [pve-devel] [PATCH qemu-server 1/1] fix #6613: pass purge param to delete_service_from_config Michael Köppl
2025-09-17 11:53 ` [pve-devel] [PATCH container " Michael Köppl
2025-09-17 11:53 ` [pve-devel] [PATCH manager 1/2] ui: add SafeDestroyResource window Michael Köppl
2025-09-23 7:50 ` Daniel Kral
2025-09-17 11:53 ` [pve-devel] [PATCH manager 2/2] ui: use SafeDestroyResource window for removing resources Michael Köppl
2025-09-23 7:50 ` Daniel Kral [this message]
2025-09-23 8:56 ` Michael Köppl
2025-09-17 11:53 ` [pve-devel] [PATCH docs 1/1] add notes about effects of purge flag for resource and guest removal Michael Köppl
2025-09-23 8:04 ` [pve-devel] [PATCH container/docs/ha-manager/manager/qemu-server 0/7] fix #6613: update HA rules upon resource deletion Daniel Kral
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=DD00KSC99GK3.3VQ3Z9BA0TS0D@proxmox.com \
--to=d.kral@proxmox.com \
--cc=pve-devel-bounces@lists.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