Feature #14604
closedCreate/update composite content-view by content-view Names
Description
[RFE] Create/update composite content-view by content-view Names . Currently it works fine with the version ID's
3. What is the nature and description of the request?
Option to add content views to the composite view by name rather than just by ID number.
Currently its only possible using IDs.
Create:
hammer> content-view create --name='testcomposite' --component-ids='4,2' --organization-id=1 --composite
Update:
hammer> content-view update --name RHEL6+RHEL7 --component-ids 2 --organization-id 1
---------------------------------------------
hammer> content-view create --help
Usage:
content-view create [OPTIONS]
Options:
--component-ids COMPONENT_IDS List of component content view version ids for composite views
Comma separated list of values.
---------------------------------------------
hammer> content-view update --help
Usage:
content-view update [OPTIONS]
Options:
--component-ids COMPONENT_IDS List of component content view version ids for composite views
Comma separated list of values.
---------------------------------------------
4. Why does the customer need this? (List the business requirements here)
Cu words: "I'm creating the views with a set of scripts and do not have direct knowledge of the component ids. They can be derived, but everything else under this command takes either the ID or the Name. It would reduce the complexity of my tools if this option were supported."
5. How would the customer like to achieve this? (List the functional requirements here)
Hammer command with 'name' option for composite views.
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
Satellite 6.2
9. Is the sales team involved in this request and do they have any additional input?
No
10. List any affected packages or components.
Hammer
11. Would the customer be able to assist in testing this functionality if implemented?
yes