Most of the CLI will take in --target as one of the options, yet, we
don't have a command to show what targets are available to be supplied
to the command.
User can do 'list-clusters' to list out all the clusters, but there
doesn't seem to be a way to list out just stand-alone instances.
'list-instances' list out ALL instances, whether it is in a cluster or
not.
If we have a 'list-targets' command, which list out all the cluster
and standalone instances, that will enhance usability.
More importantly, once we have REST wrap this command, GUI can call
that and show this list as available targets easily. As of now, I
have to
1. make a call to get all the instances
2. make another call to get all the clusters
3. loop through the clusters, call each to get all the server-ref under
it, then filter out those instances that i got from #1 above so i can
get the standalone instance list.
4. combine the list of clusters and standalone instances to construct
the final list for targets
I hope that the above logic can be done in the admin backend, it can be
shared by other client, (will ide need this ? ) and also save the
multiple calls that GUI needs to make.
If there is an easier way to get the list of targets, please let me know.
I need this list of targets for application deployment and resources
creation.
One issue maybe the 'target' option for creating config elements. I
checked v2 CLI, it says "Valid target types are cluster,
configuration, unclustered server instance, domain administration
server". If they supply any of the targets thats returned by the
'list-target' command, that will still work, but they will not see the
configuration name under 'list-targets'. Maybe we can call it something
else other than 'list-targets' ?
Another question is whether 'server' should be included in
'list-targets'. Currently 'list-instances' does not return
'server', but it is a valid target.
Thoughts ?
thanks
Anissa.