Bug 855267 - [RFE] in "product" CLI commands add new option "product_id"
[RFE] in "product" CLI commands add new option "product_id"
Product: Red Hat Satellite 6
Classification: Red Hat
Component: API (Show other bugs)
Unspecified Unspecified
unspecified Severity high (vote)
: Unspecified
: --
Assigned To: Brad Buckingham
Hayk Hovsepyan
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2012-09-07 03:24 EDT by Hayk Hovsepyan
Modified: 2014-09-18 12:42 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
As product name is no longer unique (i.e. multiple products may have the same name), the user needs to provide a unique identifier for the product when using the command line interface. This update allows users to alternatively provide a product label or ID in place of a product name.
Story Points: ---
Clone Of:
Last Closed: 2012-12-04 14:52:35 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Hayk Hovsepyan 2012-09-07 03:24:11 EDT
Description of problem:
As the name of product is not unique anymore, it does not make sense to do operations with product by it's name in CLI.
It needs new option "product_id" added instead on "name" in product CLI.
Like the "product update --name --org --description" it should be 
"product update --product_id --org --description".
And the same for all product commands.
Comment 1 Mike McCune 2012-10-03 11:24:55 EDT
this will most likely be addressed in the following bug that makes product name unique:

Comment 2 Mike McCune 2012-10-09 16:05:49 EDT
This is a blocker since the CLI and API will no longer function with non-unique product names.
Comment 3 Brad Buckingham 2012-10-10 10:33:28 EDT
This issue appears to affect the following CLI commands which use product name:

changset: update
errata: list
product: update, delete, synchronize, status, cancel_sync, add_filter, list_filters, remove_filter, promote, set_plan, remove_plan
repo: create, discover, list
Comment 4 Brad Buckingham 2012-10-15 13:17:16 EDT
In order to address this bugzilla, we are adding the ability for the user to specify product name, label or id in the various commands where products are currently specified.  Since the same name may be used for multiple products, users may want to use product id always; however, names remain supported for backward compatability.

That said, if product name or label is provided and multiple products exist with that name/label, the user will receive an error message similar to:

   "More than 1 product found with the name or label provided, recommend 
    using product id.  The product id may be retrieved using the 'product
    list' command."

Prior to the changes, the CLI would always use the 'first' product that matched, which can result in unexpected behaviors.

This bugzilla affects several commands, such as the following:

- product update
- product add_filter
- product list_filters
- product remove_filter
- product set_plan
- product remove_plan
- product synchronize
- product status
- product cancel_sync
- product promote
- product delete

- changeset update (includes --add_product, --remove_product and --from_product)

- errata list
- errata info

- package list
- package info

- repo create
- repo discover
- repo list
- repo status 
- repo info
- repo update
- repo synchronize
- repo cancel_sync
- repo enable
- repo delete
- repo list_filters
- repo add_filter
- repo remove_filter
Comment 5 Brad Buckingham 2012-10-22 10:28:59 EDT
katello github pull request:

Comment 8 Hayk Hovsepyan 2012-10-24 04:41:25 EDT
Verified on revision:

product_id parameter is added for all mentioned commands and it works correctly.
Comment 10 errata-xmlrpc 2012-12-04 14:52:35 EST
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.

Comment 11 Mike McCune 2013-08-16 13:54:16 EDT
getting rid of 6.0.0 version since that doesn't exist

Note You need to log in before you can comment on or make changes to this bug.