BIND 10 #384: Bindctl doesn't show complicated config structures

[BIND 10 Development]

#384: Bindctl doesn't show complicated config structures
---------------------------+------------------------------------------------
      Reporter:  vorner    |        Owner:     
          Type:  defect    |       Status:  new
      Priority:  major     |    Milestone:     
     Component:  bind-ctl  |   Resolution:     
      Keywords:            |    Sensitive:  0  
Estimatedhours:  0.0       |        Hours:  0  
      Billable:  1         |   Totalhours:  0  
      Internal:  0         |  
---------------------------+------------------------------------------------

Comment(by jelte):

 Right.

 In some ways, this is simply incomplete; there is no way to address items
 in a list.
 In other ways, bindctl is 'too smart'; it tries (badly) to make pretty
 results, thereby hiding essential data.
 The first problem also makes it harder (or impossible) to get for instance
 default values.

 I also found another problem in the parser, in that it sometimes
 erroneously sticks a '/' at the end of a key in a map.

 For the first item, I propose to add this feature;
 - For list elements, individual items can be addressed with [i], where i
 is the element number.
 - I think we then also want some form of getIdentifier(); given a piece of
 data, and some context, return the full identifier to that piece of data.

 There is an optional 'advanced' thing i'm half thinking of, since lists
 will probably often contain map elements, perhaps we also want some form
 of 'primary key' in these maps, that we can use directly in addressing.
 However, this is a. perhaps not really intuitive, and b. would mean that
 that key be a string, and unique. (for instance, if you have a list of
 zones somewhere, where 'zone' contains other info, you'd be able to use an
 identifier like 'my_module/zones/example.com/masters', where 'example.com'
 is obviously not a built-in name but an element of the map in the list
 my_module/zones).

 For the second item; I propose I remove the 'smartness' and reduce it to
 two options; either print only 1 'level' of config/data/whatever, or print
 it all completely in JSON format (so you can copy paste back into input if
 you want).

-- 
Ticket URL: <http://bind10.isc.org/ticket/384#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development