You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not a big fan of these kinds of prompts, since I issue the command, since I know what I want it to do (unix philosophy).
If we do a prompt, there needs to be a -f flag to make sure it does not prompt, if not wanted.
bkircher
changed the title
add batch operation to gscloud
Allow deleting multiple objects at once
Feb 10, 2021
My stance: just use the shell for looping over all objects, that what it is build for 🙃
But wouldn't fight this if this is getting added directly to gscloud . As long it doesn't get too crazy. Suggestion:
We call it differently then normal commands, e.g. as in Docker CLI spirit we would call this prune:
$ gscloud server prune # or
$ gscloud storage prune
This could by default remove dangling objects (servers w/o storage, un-assigned IP addresses, storages w/o servers attached).
There we could add a --all flag that would just purge all the things in that project.
$ gscloud server prune --all # removes all servers, storages, IP addresses
If we do a prompt, there needs to be a -f flag to make sure it does not prompt, if not wanted.
Yes. We have --force flags already in the form of gscloud-storage-set(1): For potentially destructive operations like changing storage capacities:
$ gscloud storage set --capacity 9 3fe7441e-7012-4e0c-9fd9-7a86795fd4fe
Downsizing can destroy your data. Re-run with --force to reduce storage size
from 10 GB to 9 GB
The command would do nothing unless --force is passed
$ gscloud storage set --capacity 9 --force 3fe7441e-7012-4e0c-9fd9-7a86795fd4fe
the idea would be to remove all objects in a projects like
gscloud servers power off -all
gscloud storages rm --all
gscloud servers rm --all
there should be a "are you sure" prompt
furthermore gscloud should check if all servers are off, before running
ideas?
The text was updated successfully, but these errors were encountered: