Bug 595758

Summary: subscription-manager-cli regtokens vs subscription numbers
Product: Red Hat Enterprise Linux 6 Reporter: wes hayutin <whayutin>
Component: subscription-managerAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED NOTABUG QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: low    
Version: 6.1CC: shaines, spandey
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-22 18:26:36 UTC Type: ---
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: 568421, 616906    

Description wes hayutin 2010-05-25 14:49:54 UTC 
Description of problem:

[root@iolo ~]# subscription-manager-cli subscribe --help
Usage: subscription-manager-cli subscribe [OPTIONS]

subscribe

Options:
  -h, --help           show this help message and exit
  --debug=DEBUG        debug level
  --product=PRODUCT    product ID
  --regtoken=REGTOKEN  regtoken
  --pool=POOL          Subscription Pool Id


I am wondering if we should include the term "subscription number" or what ever "official" term is sent to customers in addition to regtoken.

a suggestion:

Options:
  -h, --help           show this help message and exit
  --debug=DEBUG        debug level
  --product=PRODUCT    product ID
  --regtoken=REGTOKEN  regtoken or subscription number or "official term"
  --pool=POOL          Subscription Pool Id

OR

Options:
  -h, --help           show this help message and exit
  --debug=DEBUG        debug level
  --product=PRODUCT    product ID
  --subscription-number=subscription number  subscription number or regtoken
  --pool=POOL          Subscription Pool Id
Comment 2 wes hayutin 2010-07-22 18:26:36 UTC 
this is as designed right now