Option to delete files when deleting multiple images / snapins.
I had previously mentioned this on another thread, https://forums.fogproject.org/topic/12148/replication-problems-1-5-4-always-copying/42, but @Sebastian-Roth suggested I post it here instead…
So, if you go to delete one or more snapins / images from the list of all snapins / all images, it will not remove the files associated with whatever you delete. In order to do so, you must enter each image / snapin individually, go to the delete tab, and check the box to delete files when deleting. It would be nice to have on the all images / snapins pages for mass changes as I have had to explain to my team that only the aforementioned method will give them the results they are expecting.
Please include this option:
I am not sure how hard it would be to implement these changes, but it would save time having to go in and delete files manually because someone deleted an old image the wrong way.
Wayne Workman last edited by
I really like the idea although it would mean that users need to confirm twice.
I think it’s fine. It’s like Tom said, very serious to mass delete images.
Perhaps fog can tell you how many images you’re about to delete, and ask you to confirm that by entering the number of images it’s displaying. Say it’s 12 images, so you’d have to type 12 into a textbox to confirm.
I really like the idea although it would mean that users need to confirm twice. Type in the number and authentication details.
Any further comments before I add this to the (end of the) stack of things to add in the following weeks?
Wayne Workman last edited by Wayne Workman
Let’s say, for example, you selected 12 images
In that case, the admin has selected 12 images for deletion. A confirmation would be appropriate to confirm. In some other softwares concerning deleting something very important, the interface usually prompts for the user to enter in something to confirm beyond doubt.
- Github requires you to type in the full repo path to delete a repo.
- Terraform requires you to type in ‘yes’ to destroy infrastructure. (and warns you there is no undo)
Perhaps fog can tell you how many images you’re about to delete, and ask you to confirm that by entering the number of images it’s displaying. Say it’s 12 images, so you’d have to type
12into a textbox to confirm.
@Tom-Elliott You’re right, I hadn’t considered that. My apologies. I guess I have been blinded by my obsession with reducing clutter and streamlining processes. I have a team of techs that use our FOG server and it seems to be a common error to delete an image / snapin without going in individually to delete with files. I was trying to reduce clutter on the back-end and having to go in and clean things up from people deleting the wrong way. Guess I need to start creating some in-house documentation on proper FOG procedures…
@jflippen Because sometimes you may have a image captured for forensic reasons. You capture the disk in its current state, and remove the definition to ensure it can’t be messed with?
Again, I’m not saying we can’t add it. The nature of “en mass” delete however leaves for a lot of error.
Let’s say, for example, you selected 12 images, and only meant to select 5. If you do the delete on all of them, it will delete all 12 images. Poof, Gone.
@Tom-Elliott If that is the case, why even include delete image on the list all page? I can’t imagine wanting to delete multiple images but keep their files. I understand wanting to make something idiot-proof but having a delete image that doesn’t delete the files seems unintuitive to me.
IT’s that same reasoning (of thought and worry) that I didn’t include the functionality in the first place.
@Tom-Elliott What do you think about this? I am a bit worried that people would hurt themselves but on the other hand they could even using the single delete option anyway.