Confman mercurial extension
Confman provides simple means to specify and record configuration
histories. The configurations that are entirely made of tags are
The point of baseline maintenance is the ability to reproduce
By also accepting arbitrary changesets, one can record the
construction history of a baseline and exchange intermediate steps.
Once you are done reading this overview, you might want to read the
- git (optional, for managed git repositories)
- requests python library (optional, to use .tgz or .zip files as repositories)
A confman specification is all contained within the
.hgconf file with two managed repositories:
[yams] pulluri = http://hg.logilab.org/yams layout = yams track = yams-version-0.34.0 [logilab.common] pulluri = http://hg.logilab.org/logilab/common layout = logilab/common track = stable hgrc.paths.review = ssh://hg.logilab.org/review/logilab/common
track attribute can point to a
changeset id or a to a
revset. This is how the baseline is declared.
Updating the baseline (i.e. providing new values to the
attribute if present) can be performed automatically with the
cfsummary print a summary of the managed repositories cfensure clone, pull and update the managed repositories (according to their track value) cfbaseline update any track attribute with a tag (if possible) or a changeset id
If the track attribute is missing or contains a branch name or a revset,
cfbaseline does nothing.
If the track attribute contains a branch name or a revset,
cfbroadcast send a shell command to any managed repository cfpull pull repositories cfpush push repositories up to their current track cfarchive create an unversioned zip archive of configuration repositories at revision specified by their track (or default if not specified) cffiles list tracked files of the managed repositories whose name in the working directory matches the given patterns
An application configuration includes the entries of some of its
dependencies, for instance a web framework.
Rather than copy-and-pasting configuration entries in each app that
depends on the framework, we can build a configuration for the
framework and reuse it from the application's configurations.
Hence we have
Let's do with a small example:
[conf.cubicweb] pulluri = http://hg.logilab.org/grshells/grshell-cubicweb layout = conf.cubicweb track = cubicweb-3.19.2 expand.whitelist = cubicweb rql yams logilab-common logilab-database logilab-mtconverter logilab-common [cube.timeseries] pulluri = http://hg.logilab.org/cubes/timeseries layout = cubes/timeseries track = cubicweb-timeseries-version-1.10.1 [cube.weathermap] pulluri = http://bitbucket.org/auc/weathermap layout = cubes/weathermap track = 0.2.0
In this, we build a configuration for a weather forecasting app using:
- the cubicweb configuration maintained by the CubicWeb maintainers,
timeseriescube (a CubicWeb component or plugin),
expand.whitelist=<...> or lastly
expand.blacklist=<...> notations indicate a repository that contain
a configuration and should be used by
confman as such.
Here's a real-life configuration tree:
Confman can manage a tarball (
.tar.bz2) as a managed repository.
Note that only basic feature is supported for now: the tarball is downloaded and
uncompressed automatically if the corresponding
layout is missing.
Confman has experimental git support. Top-level configurations must reside in a mercurial repository.
The guestrepo mercurial extension was born at the same time as
confman and both provide roughly the same basic services (though,
guestrepo does not handle well recursive configurations).
confman can read and write
guestrepo configuration repositories as
well as its own.
Additionally, it is possible to
as examplified above (the cubicweb configuration is currently
guestrepo and its file format).
When working on a
guestrepo configuration, it is possible to use the
cfbaseline --force-hgconf command to generate a valid confman