-
Notifications
You must be signed in to change notification settings - Fork 9.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
etcdctl recursive delete with wildcards #2385
Comments
We have remove recursively functonality:
|
what about the wild-cards? --recursive removes the key and all child keys(if it is a directory) |
@timothysc What you want here is the ability to do this: Give the following keys:
After running the following command:
You want the following keys to exist:
Does that look right? |
@kelseyhightower yup. |
I ended up here looking exactly for what's requested. I ended up doing a |
@olibob great minds think alike ;-) Anyway... I know upstream is not to keen on treating it as a file-system, but users would ideally like to perform all the traditional ops. IMHO a fuse mount would enable, and folks could just say they will not support the entirety of POSIX semantics. Then I could just perform traditional shell commands and be done with it vs. trying to force fit through etcdctl |
Sounds like I'm not the only one that wants etcdctl to become a full-fledged etcd CLI client... |
👍 |
Just chanced across this, but wouldn't the shell fill in the |
I am inclined to close this. We do not actively working on v2 anymore. v3 does not support the concept of dir, so this is not an issue anymore. |
sgtm |
For etcd v3 use That will delete everything starting with |
There are times where is would be very useful to recursively delete based on wildcard.
e.g. rm -rf /foo/bar/*
The text was updated successfully, but these errors were encountered: