[bind10-dev] Migration of configuration

[Michal 'vorner' Vaner]

Hello

Once again with #2911, there'll be incompatibility in configuration that may
need the user to manually edit the JSON config file. I believe it is high time
we do something about this in generic manner, since there'll be no end of these.

I have two proposals.

Pretty-print the JSON file
==========================

This is not a real solution. But when the user needs to modify it manually, it
can be made easier by pretty-printing the JSON, so we don't have one long line.
The current state is only slightly better than a binary file, since it is
completely unreadable.

I fear JSON doesn't support comments (which is one big disadvantage over XML).
If it did (or if we found a way to attach comments), we probably could also
attach the description from the spec files to the options.

Having migration scripts
========================

We need some kind of (semi)-automatic way to migrate the configuration. Scripts
to migrate from version X to version Y, either sitting in some well-known
directory or embedded in the spec files. They could be chained to do upgrade
across multiple versions (and possibly downgrade). Something the user may run
and let the configuration be fixed for him, possibly by asking few simple
questions.

It could be something similar to our dbutil.

Does it make sense to schedule at least some of that to some near sprint? The
first one (the pretty-printing) could possibly be adding the correct parameter
to the JSON dumper.

With regards

-- 
If you are over 80 years old and accompanied by your parents, we will
cash your check.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20130529/ce652ed3/attachment.bin>