| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Set default value to false.
Made the find_and_replace calls multilined.
|
| |
|
|
|
|
| |
Run with -h to see all the options.
|
| |
|
|
|
|
|
|
| |
Includes Pyversion() class which simplifies getting the Python version
that Bcfg2 is running under. It is mostly useful for Python 2 and under,
since Python 3 has the handy sys.version_info.{major,minor,...} object.
|
| |
|
|
|
|
| |
Minimal testing has been done to compare export.py and export2.py.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
The command "bcfg2-info generators" didn't spit out anything useful,
just an unexpanded $Id$ keyword for each of the current generators.
It's been that way for quite some time now, and nobody seemed to miss
the command.
|
| |
| |
| |
| |
| | |
Also switched to use __longhelp__ instead of __shorthelp__, as
__shorthelp__ isn't actually very helpful.
|
|/
|
|
|
|
|
|
|
|
| |
By default, bcfg2-admin viz creates a diagram that shows the complete
contents of the repository: all Groups, Bundles, and (optionally)
Hosts/Clients. In a complicated configuration, this can be an
overwhelming amount of information.
This change adds an --only-client option that can be used to limit the
elements on the diagram to those that apply to the named host.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Indent all output in a consistent way.
|
|
|
|
|
| |
When the "-r" flag is used, check for files which are present in the old
directory but not in the new directory (not just the other way round).
|
|
|
|
| |
Fix the messages which are spit out when the "-r" flag is used.
|
|
|
|
| |
... in the compareSpecifications() method.
|
|
|
|
|
| |
Check for bundles specified in the old configuration but not in the new
configuration (not just the other way round).
|
|
|
|
|
| |
If the configuration specifications contain multiple <Independent> tags,
compare all of them, not only the first one.
|
|
|
|
|
| |
Iterate only once over the entries of a bundle and print a single
two-line message for each differing or missing entry.
|
|
|
|
|
| |
Removing elements from a list while iterating over it (forwards) leads
to unexpected results.
|
|
|
|
|
| |
The if statement which checks whether a given tag is known was declared
the wrong way round.
|
|
|
|
|
|
|
|
| |
Let "bcfg2-admin compare" handle POSIX <Path> tags instead of the
old-style entries.
While at it, add support for all attributes which might show up in
configuration specifications.
|
|
|
|
|
| |
The __call__() method now calls self.compareSpecifications() instead of
effectively doing nothing.
|
|
|
|
|
| |
Remove the "reloc" <Package> attribute from the documentation and from
the XML Schema, as it is no longer supported (since commit 7beb2f08d8).
|
|\ |
|
| |
| |
| |
| |
| | |
Nesting Bundle tags is now allowed in order to support XInclude within
Bundles.
|
|\ \ |
|
| |/
| |
| |
| | |
This wasn't originally anticipated, but if a repository is updated via rsync, HandleEvent() receives 'changed' actions for directories as well. Directories aren't present in self.entries and consequently caused KeyErrors.
|
|\ \
| |/
|/| |
|
| | |
|
| | |
|
|/
|
|
|
|
| |
Let the Statistics plugin raise a PluginExecutionError if a "sensitive"
entry is requested by "bcfg2-admin pull". This is how the DBStats
plugin behaves already.
|
|
|
|
|
| |
The internal database version must be incremented due to the new
"is_sensitive" column.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|\ |
|
| |
| |
| |
| |
| | |
Catch I/O errors which might occur while reading a file specified as
argument to --badentry, --extraentry, or --modifiedentry.
|
| |
| |
| |
| |
| | |
On getopt errors, print a proper usage message instead of spitting out a
traceback.
|
| |
| |
| |
| |
| |
| | |
The new "entry.reason.is_sensitive" flag indicates whether the file
contents/diffs were omitted from the database due to the "sensitive"
<Path> attribute.
|
|/
|
|
|
|
| |
The contents/diffs of <Path>s which are marked as "sensitive" are now
omitted from the reports transmitted to the server, so that they won't
end up in the statistics database.
|
|
|
|
|
| |
The possible and default values of the "important" and "paranoid"
attributes weren't listed correctly.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|\ |
|
| |\ |
|
| | | |
|
| |\ \ |
|
| |\ \ \ |
|
| | | | | |
|
| |_|_|/
|/| | |
| | | |
| | | |
| | | | |
Handle the removal of :info files in the same way as the removal of info
files (without leading colon) is handled.
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|