BIND 10 #1788: update auth spec to specify in-memory "filetype" with sqlite3 backend

[BIND 10 Development]

#1788: update auth spec to specify in-memory "filetype" with sqlite3 backend
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  medium        |                    Milestone:  Next-
           Component:  b10-auth      |  Sprint-Proposed
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:  xfr
         Total Hours:  0             |  for in-memory
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 This is a subtask of #1787.

 We'll update the b10-auth spec so we can specify the "type" of
 in-memory data source file.  This is the current spec:
 {{{
           { "item_name": "zones",
             "item_type": "list",
             "item_optional": false,
             "item_default": [],
             "list_item_spec":
             { "item_name": "list_element",
               "item_type": "map",
               "item_optional": true,
               "item_default": { "origin": "", "file": "" },
               "map_item_spec": [
               { "item_name": "origin",
                 "item_type": "string",
                 "item_optional": false,
                 "item_default": ""
               },
               { "item_name": "file",
                 "item_type": "string",
                 "item_optional": false,
                 "item_default": ""
               }]
             }
 }}}

 I propose adding "filetype" item.  Its optional and the default is "text".
 If it's "sqlite3", the specified "file" will be assumed to be an
 SQLite3 database file, and some underlying magic (which will go to a
 separate task) loads the zone content via the SQLite3 data source to
 in-memory.

 In this task we only extend the spec file and update the configuratation
 parse validation to accept it.  We don't actually use it yet.

 There is no dependency for this task.

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