j3d1/webvirtcloud
1
0
Fork 0
mirror of https://github.com/retspen/webvirtcloud synced 2026-11-09 03:36:48 +00:00
Code Issues Projects Releases Wiki Activity

fix(templates): each delete page says what deleting its object does

Browse source 
The shared delete page asked only whether to delete the object. Each
view now gives its consequence: a deleted compute's VMs keep running
but the panel forgets them and their owners, a deleted user's VMs
stay, a group's members keep their accounts, a VM's owner loses only
the access, a removed VM's record no longer brings its owners back,
an SSH key stays on the VMs that have it, a flavor only goes as a
size template.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
catborise 2026-10-22 11:02:54 +03:00
parent f9c8c36a6b
commit fbe93d9aee
6 changed files with 54 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

8
admin/views.py
View file

@ -76,7 +76,7 @@ def group_delete(request, pk):
return render(
request,
"common/confirm_delete.html",
{"object": group},
{"object": group, "consequence": _("Its members stay but lose the permissions it gave them.")},
)
@ -182,7 +182,8 @@ def user_delete(request, pk):
return render(
request,
"common/confirm_delete.html",
{"object": user},
{"object": user,
"consequence": _("Their access to VMs, SSH keys and settings go; the VMs themselves stay.")},
)
@ -237,7 +238,8 @@ def tombstone_delete(request, pk):
return render(
request,
"common/confirm_delete.html",
{"object": tombstone},
{"object": tombstone,
"consequence": _("Its owners no longer get the VM back if its UUID shows up again.")},
)