Bug 1032917 - Allow CLI tab completion to follow management model references
Allow CLI tab completion to follow management model references
Status: NEW
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Brian Stansberry
Petr Kremensky
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-21 04:08 EST by Petr Kremensky
Modified: 2017-10-09 20:18 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Feature Request
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Petr Kremensky 2013-11-21 04:08:54 EST
Description of problem:
 One can configure auto-start, cpu-affinity, group, priority, socket-binding-group, and socket-binding-port-offset when adding new server into domain. There is tab completion only for auto-start attribute. We should add some tab completion help at least into group and socket-binding-group to make CLI more usable.

Version-Release number of selected component (if applicable):
 6.2.0.CR3

Steps to Reproduce:
 1. Start out-of-box domain and connect to CLI
 2. Try auto completion with tab on socket-binding-group and group attributes
    ./host=master/server-config=server-four:add(socket-binding-group=
    ./host=master/server-config=server-four:add(group=

Actual results:
 Nothing
 
Expected results:
 CLI will show possible attribute values
Comment 2 Brian Stansberry 2013-11-21 08:50:43 EST
The requested feature comprises 3 elements:

1) The fundamental piece: for attributes that represent references to other model elements, the static management model description metadata should describe the exact nature of that reference. For instance, that the "group" attribute in a server-config resource is a reference to the value portion of the last element in the address of a /server-group=<thevalue> resource. 

2) Optional: the management API should provide some standard mechanism for querying the legal values for the attribute on the server side. This is optional (at least for this particular feature request), as the client can use the metadata from 1) to figure out how to obtain the data using the existing API (e.g. /:read-children-names(child-type=server-group)).

3) The CLI should take advantage of 1) and perhaps 2) during tab completion.

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