Bug 1032917

Summary: Allow CLI tab completion to follow management model references
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Petr Kremensky <pkremens>
Component: Domain ManagementAssignee: Brian Stansberry <brian.stansberry>
Status: CLOSED EOL QA Contact: Petr Kremensky <pkremens>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: dandread, ochaloup
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:47:21 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Petr Kremensky 2013-11-21 09:08:54 UTC
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 13:50:43 UTC
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.