catborise 887b807451 fix: a network, pool or secret a VM needs is not stopped or deleted ... Stopping a network cut the running VMs on it off, deleting one or a secret kept the VMs that name it from starting, and stopping a pool took the disks of running VMs away, all without a word. Each is now refused with the VMs (and, for a secret, the pools) that need it: stopping while a running VM uses it, deleting while a VM's definition names it. A disk given by its file path does not need its pool's definition. The API's pool stop is refused the same way. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>		2026-10-22 08:34:55 +03:00
..
__init__.py	fix(virtsecrets): a secret's usage value goes into its XML as text	2026-10-19 16:43:06 +03:00
test_create_secret.py	fix(virtsecrets): the create dialog offers only the usage types it can create	2026-10-20 22:37:51 +03:00
test_live_secrets.py	fix(virtsecrets): a secret's usage value goes into its XML as text	2026-10-19 16:43:06 +03:00
test_secret_in_use.py	fix: a network, pool or secret a VM needs is not stopped or deleted	2026-10-22 08:34:55 +03:00
test_secrets_page.py	fix(virtsecrets): a secret's value never reaches the page	2026-10-20 22:37:36 +03:00