GitLab

No real change, just sorting the messages in the message file.

Provide descriptions for log messages added in the previous commit, the
ones for more detailed logging during update of database based
datasource.

Provide the data being updated and operations on database based
datasources.

Applied verbatim from the mailing list.

For the previous commit, adding the reverse name to the list of
parameters for delete.

This is significantly faster, as the rname has an index on it, while the
name doesn't.

Applied verbatim as sent on the mailing list. Documentation will come
soon.

some compilers claim it causes a copy whie it's defined non copyable,
triggering an error.  this fixes some build failure reported by the bots.
should mostly trivial, so committing at my discretion.

acknowledged on jabber

(used tools/reorder_message_file.py)

instead of the "static" BIND zone.  there's no difference between these two
any more, so this is just a matter of style.

may need some more discussion, but not the point for this branch anyway,
and at least it's more consistent with rest of the source code.

Okayed via jabber yesterday.

I am not adding a changelog entry as it is minor.

we can do everything that the dedicated static data source did with
"MasterFiles" type of data source with preconfigured parameters.
this cleanup is not directly related to the subject of this task, but
will make later changes simpler.

this is not a program error, so CacheConfigError should be more appropriate.

that would be better abstraction.  also remove getLoadAction for now as
we won't implement it in this task.

also simplified the constructor interface; we actually don't need the
other one.

it now doesn't log it for each zone but only warns about the entire data
source.

as details are implemented the latter now seems more appropriate for the
responsibility of this class.

this eliminated the need for if-else cases in
ConfigurableClientList::configure().  to make it possible getDataSourceClient()
was slightly updated so that it recognizes "MasterFiles".

... as the methods are private anyway.

for trac 2719 in b10-dhcp6.

the actually behavior is still same: it only supports the "local" segment.