| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
combine config files
get full stack trace from failed plugins for easier troubleshooting
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
| |
These are enabled by default on Ubuntu installs, so it makes sense to
add them here in case the dependency paths are different.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
| |
* fixed detection of RHEL version and python Sphinx path
* added XSL file to do XSLT transform for build_dtddoc
|
|
|
|
|
|
| |
* fixed bcfg2-lint bug with older pythons
* made bcfg2-lint silent by default on success
* adjusted bcfg2-lint defaults and alerting levels to work better out-of-the-box
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
|
|
| |
* Changed all references to bcfg2-repo-validate in the documentation
to bcfg2-lint
* Wrote man pages for bcfg2-lint and bcfg2-lint.conf
* Cleaned up straggling references to bcfg2-repo-validate in
Makefiles, spec files, and the POSIX tool
* A few minor bug fixes
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
|
|
| |
interface to be lots more flexible and extensible. Added several more
tests. If bcfg2-lint is run as bcfg2-repo-validate, it roughly
emulates the functionality of that program.
TODO: Need to figure out correct way to symlink bcfg2-repo-validate to
bcfg2-lint on install.
|
|
|
|
|
|
|
|
| |
To use, add "Systemd" to the "drivers" option in the "client" section
of bcfg2.conf on the client. Then, define services on the server like
this:
<Service name="rabbitmq-server" status="on" reload="restart" type="systemd"/>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|\ |
|
| |
| |
| |
| | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|/
|
|
| |
group file
|
| |
|
|\ |
|
| |
| |
| |
| | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | |
|
|\| |
|
| |\ |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | |
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
"Properties/foo.xml" and "Properties/foo.xsd") which specifies a
schema for that property file. bcfg2-repo-validate will check the
property file against its schema.
Updated bcfg2-repo-validate man page with several new options.
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Preliminary support for version control checkouts onto the client. This
client tool is still fairly picky and has some known problems (incorrect
git index file, for one). All the abstraction libraries left quite a bit
to be desired. Also, none were packaged in popular distributions.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|/
|
|
|
|
| |
* bcfg2-repo-validate does not chase XIncludes if --stdin has been
specified, but just validates the Metadata files you provide on
stdin
|
|
|
|
|
|
|
|
|
| |
This allows for verification of specified services, but skips
installation completely when mode is set to manual. This means that
incorrect services will still show up in reports, but they won't be
modified in an automated way.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
|
| |
Python < 2.6 uses the '0600' format for specifying the mode while 2.6
and later allow the use of '0o600'. Since python 3 forces the latter, we
can use the stat module to maintain compatibility with both.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
pre-3.0 versions of python
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Quoted from PEP 3114:
The iterator protocol in Python 2.x consists of two methods:
__iter__() called on an iterable object to yield an iterator,
and next() called on an iterator object to yield the next item in
the sequence. Using a for loop to iterate over an iterable object
implicitly calls both of these methods. This PEP proposes that the
next method be renamed to __next__, consistent with all the other
protocols in Python in which a method is implicitly called as part
of a language-level protocol, and that a built-in function named
next be introduced to invoke __next__ method, consistent with the
manner in which other protocols are explicitly invoked.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|