| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
* Fixed mode argument parsing when a config file is supplied
* Fixed loading help messages when Reports is not configured
* Improved option parsing; used Bcfg2.Options.OptionParser
|
|
|
|
| |
altsrc'd files
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Remove the --raw option from the "bcfg2-admin viz" documentation. The
option has been superseeded by the --outfile option which allows for
specifying arbitrary output types since commit 476cb9ac76.
|
|
|
|
|
| |
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.
|
|
|
|
| |
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.
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
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.
|
|\ |
|
| |\ |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
Replaces PluginExecutionError with Bcfg2.Server.Plugin.PluginExecutionError. Reported by emias.
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\| | |
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | |\ \
| | | | |
| | | | | |
import sys for SGenshi and Bundler
|
| | | | | |
|
| | | | | |
|
| | |\ \ \
| | | |/ /
| | |/| | |
Two small fixes for Ldap plugin
|
| | | | | |
|
| | | | | |
|
| | |/ / |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
(cherry picked from commit 071ef1a1fbe6368b1abb81855e1ab95e316e6911)
|
| | | | |
|
| |_|/
|/| |
| | |
| | |
| | | |
Handle the removal of :info files in the same way as the removal of info
files (without leading colon) is handled.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This feature allows you to use the on-disk permissions of the file in
the Cfg repository rather than specifying them using the traditional
means in info.xml.
Note that this only works for the octal permissions of the file on disk
since the owner/group may not exist on the destination machine.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|