BIND 10 #3027: the existance of child configuration elements doesn't imply the existance of the parents

[BIND 10 Development]

#3027: the existance of child configuration elements doesn't imply the existance
of the parents
-------------------------------------+-------------------------------------
            Reporter:  bconry        |                         Type:
              Status:  new           |  defect
           Milestone:  New Tasks     |                     Priority:
            Keywords:                |  medium
           Sensitive:  0             |                    Component:
         Sub-Project:  Core          |  Unclassified
Estimated Difficulty:  0             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 {{{
 > config show_json /
 {}
 > config add /Init/components b10-cmdctl
 Error: b10-cmdctl already in /Init/components
 > config show_json /
 {}
 > config show_json /Init
 null
 > config show_json /Init/components
 {"b10-stats": {"kind": "dispensable", "address": "Stats"}, "b10-cmdctl":
 {"kind": "needed", "special": "cmdctl"}}
 > config go /Init
 Error: /Init not found
 > config go /Init/components
 >
 }}}

 Configuration elements that exist aren't shown by "config show_json",
 despite it being documented as "Show ''full'' configuration in JSON
 format." [emphasis added].

 It's also counter-intuitive that child elements can exist and be navigable
 without their parent elements existing and being navigable.

-- 
Ticket URL: <https://bind10.isc.org/ticket/3027>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development