[bind10-dev] Config snapshots in git
Michal 'vorner' Vaner
michal.vaner at nic.cz
Thu Sep 5 11:46:37 UTC 2013
Hello
On Thu, Sep 05, 2013 at 05:03:15PM +0530, Mukund Sivaraman wrote:
> * Pretty printing the JSON would be nice. Currently we write out the
> b10-config.db as a single line and it's not simple to edit it (which
> is even discouraged but we do this for lettuce tests, etc.), or do a
> diff against a copy from a different time.
+1
> * Even if we version files, what purpose is the choice of git going to
> solve? The .db files are really small, and we could simply copy it to
> a backup file. If the user is supposed to run the git tools to view
> history, etc. they can also use git add, git commit, etc. without any
> support from BIND 10.
Well, the file does not necessarily have to be small, but that is not important.
I believe that juggling bunch of old „backup files“ is just cubersome from user
interface point of view. Git could give you much more insteresting features than
just „give me the version at the start of the year“, such as „when did this
change happen“?
The reason to integrate it directly in bind10 is to have it automated. I don't
find it comfortable to type config commit in bindctl and then manually config
commit on the db file. People would tend to forget. But viewing history is the
operation on itself you need to do.
But I don't insist on git specifically. I'd like to prevent us from doing our
own inferior in-house implementation instead of using existing stuff.
With regards
--
Security warning: Do not expose this email to direct sunlight.
It may lead to undefined behaviour, including possible data or life loses.
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/20130905/2b0c2efd/attachment.bin>
More information about the bind10-dev
mailing list