-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
6.10.0
-
False
-
-
False
-
CLOSED
-
500
-
Phoenix
-
-
-
Sprint 127, Sprint 128, Sprint 129, Sprint 130, Sprint 131, Sprint 132
-
Low
-
None
Description of problem:
Adding gpg-key to repo creation in hammer only has the option of passing in gpg-key-id and not gpg-key-name. This is causing failures in automation for creating repos with gpg-key-name.
Version-Release number of selected component (if applicable):
6.10_020
How reproducible:
100%
Steps to Reproduce:
1. Git a 6.10 satellite
2. Run hammer command: hammer repository create --help
Actual results:
Possible value(s): 'immediate', 'on_demand'
--gpg-key-id GPG_KEY_ID Id of the gpg key that will be assigned to the new repository
--http-proxy[-id] Name/id of a HTTP Proxy
--http-proxy-policy HTTP_PROXY_POLICY Policies for HTTP Proxy for content sync
Expected results:
There should be an option for gpg-key-name
Additional info:
Also running the command to create gives this error:
- hammer repository create --gpg-key-name something
Could not create the repository:
Error: Unrecognised option '--gpg-key-name'.
See: 'hammer repository create --help'.