BIND 10 #2131: Migrate DDNS to use Client List

[BIND 10 Development]

#2131: Migrate DDNS to use Client List
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  vorner                             |                Status:  new
                       Type:  task   |             Milestone:  Next-Sprint-
                   Priority:         |  Proposed
  medium                             |            Resolution:
                  Component:  DDNS   |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  4
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jinmei):

 * milestone:   => Next-Sprint-Proposed


Old description:

> The DDNS uses the new data source API, but it is hardcoded to create a
> sqlite3 client with the Auth/database_file file as configuration. It
> should use the global data_sources configuration and create the data
> source through a client list.
>
> This depends on #2051.

New description:

 The DDNS uses the new data source API, but it is hardcoded to create a
 sqlite3 client with the Auth/database_file file as configuration. It
 should use the global data_sources configuration and create the data
 source through a client list.

 This depends on #2051.  Needed by #2132.

--

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