Bug 1777759
Summary: | update hammer 'htttp-proxy' help text | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | vijsingh |
Component: | Hammer - Content | Assignee: | James Jeffers <jjeffers> |
Status: | CLOSED ERRATA | QA Contact: | vijsingh |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.7.0 | CC: | apatel, bbuckingham, jjeffers, kgaikwad, mbacovsk, mshira, ofedoren, pcreech, rabajaj |
Target Milestone: | 6.7.0 | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | foreman-1.24.1-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-14 13:38:38 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1774324 |
Description
vijsingh
2019-11-28 09:35:04 UTC
Since this is not an actual hammer core bug, but related to repositories management coming from hammer-cli-katello, I'm moving it to the Hammer - Content component. Hi Vijay, Changing the description for "--http-proxy HTTP_PROXY_NAME" as proposed will make it inconsistent with other existing NAME fields. We could alter it to say "Proxy name to search by"; however, the branding might cause that to get renamed to capsule which could be even more confusing. Any objection if we leave the description on NAME field alone and update just the "--http-proxy-id HTTP_PROXY_ID"? Below are the other name fields: # hammer repository create --help|grep "to search by" --gpg-key GPG_KEY_NAME Name to search by --http-proxy HTTP_PROXY_NAME Name to search by --organization ORGANIZATION_NAME Organization name to search by --organization-label ORGANIZATION_LABEL Organization label to search by --product PRODUCT_NAME Product name to search by Hi Brad, I got your point on it and sounds good to me . I am fine if we could update '--http-proxy-id HTTP_PROXY_ID' as below as well: "--http-proxy-id HTTP_PROXY_ID ID to search by" Thanks Vijay! For consistency, I am thinking to label ID withone of the below. If you have a preference, do let me know. --http-proxy-id HTTP_PROXY_ID Identifier of the HTTP Proxy or --http-proxy-id HTTP_PROXY_ID HTTP Proxy numeric identifier Existing IDs: # hammer repository create --help|grep "ID" --gpg-key-id GPG_KEY_ID Gpg key numeric identifier --http-proxy-id HTTP_PROXY_ID Numerical ID or HTTP Proxy name --organization-id ORGANIZATION_ID Organization ID --product-id PRODUCT_ID Product numeric identifier --ssl-ca-cert-id SSL_CA_CERT_ID Idenifier of the SSL CA Cert --ssl-client-cert-id SSL_CLIENT_CERT_ID Identifier of the SSL Client Cert --ssl-client-key-id SSL_CLIENT_KEY_ID Identifier of the SSL Client Key (In reply to Brad Buckingham from comment #7) > Thanks Vijay! > > For consistency, I am thinking to label ID withone of the below. If you > have a preference, do let me know. > > --http-proxy-id HTTP_PROXY_ID Identifier of the HTTP Proxy > > or > > --http-proxy-id HTTP_PROXY_ID HTTP Proxy numeric identifier > Above looks good to me however branding might cause that to get renamed to capsule? ON_QA Verified @Satellite 6.7.0 snap 8.0 [root@qe-sat6-bm1 ~]# hammer repository create --help|grep 'http-proxy' --http-proxy HTTP_PROXY_NAME Name to search by --http-proxy-id HTTP_PROXY_ID Identifier of the HTTP Proxy --http-proxy-policy HTTP_PROXY_POLICY Policies for HTTP Proxy for content sync [root@qe-sat6-bm1 ~]# hammer repository update --help|grep 'http-proxy' --http-proxy HTTP_PROXY_NAME Name to search by --http-proxy-id HTTP_PROXY_ID Identifier of the HTTP Proxy --http-proxy-policy HTTP_PROXY_POLICY Policies for HTTP Proxy for content sync [root@qe-sat6-bm1 ~]# Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:1454 |