Bug 786173 - inconsistent modify UX in wallaby shell CRUD commands
Summary: inconsistent modify UX in wallaby shell CRUD commands
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: wallaby
Version: Development
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Next Version
: ---
Assignee: grid-maint-list
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks: 783142
TreeView+ depends on / blocked
 
Reported: 2012-01-31 16:08 UTC by Will Benton
Modified: 2012-01-31 16:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 783142
Environment:
Last Closed: 2012-01-31 16:10:33 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Will Benton 2012-01-31 16:08:53 UTC
+++ This bug was initially created as a clone of Bug #783142 +++

Description of problem:
In wallaby shell commands there are some discrepancies (probably there could be more, then those mentioned below):

c) there is no need for 'modify-group', 'modify-feature' commands, they can change only names. There is no such commands for node, subsystem (for parameters there is 'modify-param' but it cannot change name)


Version-Release number of selected component (if applicable):
wallaby-utils-0.12.5-1

How reproducible:
100%

Steps to Reproduce:
see description
  
Actual results:


Expected results:
the behaviour and output will be unified for all similar wallaby commands

Additional info:

--- Additional comment from willb on 2012-01-24 10:40:18 EST ---

This should probably be split into multiple bugs, some of which will wind up WONTFIX; assigning to Rob since these commands are his wheelhouse.

Comment 1 Will Benton 2012-01-31 16:10:33 UTC
This is by design; the modify- commands exist to modify mutable metadata.  In the case of features and groups, this includes the name but little else.  For various reasons, the names of nodes and parameters are immutable.


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