Some params should be necessary when we use "barbican secret store" command
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-barbicanclient |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When you store a secret without payload, and then try to retrieve that secret's payload, you will get
raise StorePluginNotA
StorePluginNotA
Which is misleading exception and it needs to report proper error/info message, clearly telling user that the "payload is not found" or "No Payload present"
steps to reproduce the issue
1. barbican secret store
2. barbican secret get <Secret_href>
3. barbican secret get <Secret_href> --payload
Get the following trace
Traceback (most recent call last):
File "/opt/stack/
return fn(inst, *args, **kwargs)
File "/opt/stack/
return fn(inst, *args, **kwargs)
File "/opt/stack/
**kwargs
File "/opt/stack/
transport_key)
File "/opt/stack/
secret_
File "/opt/stack/
return plugin_
File "/opt/stack/
raise StorePluginNotA
StorePluginNotA
Actually, if we use "barbican secret store" command without providing a "payload", that doesn't make any sense.
So I'm going to make the "payload" param necessary when we use "barbican secret store" command.
description: | updated |
Changed in python-barbicanclient: | |
status: | New → Invalid |