The cinderclient shell writes a completion cache to ~/.cinderclient/
I believe this is intended to cache things like UUIDs so that if you run "cinder list" and see a volume with uuid "abcd..." , you can then run "cinder list a<tab>" and have bash-completion fill in the UUID.
The cinderclient shell writes a completion cache to ~/.cinderclient/
I believe this is intended to cache things like UUIDs so that if you run "cinder list" and see a volume with uuid "abcd..." , you can then run "cinder list a<tab>" and have bash-completion fill in the UUID.
This does not happen.