| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
For the doc test all (optional) dependencies have to be installed, so
the doc test is only usefull in a few special test environments.
|
|
|
|
|
|
|
|
|
|
| |
We do not want to run the test for the Server with Python2.4 and Python2.5 and
use the nose-exclude plugin to disable the Server tests based on the directory.
We do not even want to import the modules of the Server, as it might not be
possible anymore (missing dependencies or invalid syntax).
nose-exclude-0.2 breaks compatibility with Python2.5 and below (it is using the
"with open(..):" syntax), so we have to stick to the last version below.
|
|\
| |
| | |
Options: Missing config file is not a fatal error
|
| | |
|
| | |
|
|/
|
|
| |
lxml-3.7.0 requires integers as arguements for XMLSyntaxError.
|
| |
|
| |
|
| |
|
|
|
|
| |
The migration files are autogenerated and do not need code checks.
|
|\ |
|
| |
| |
| |
| | |
Newer versions of mock, does not support the CamelCase calls.
|
|\ \
| |/
|/| |
|
| |
| |
| |
| | |
generate
|
| | |
|
|\ \
| | |
| | | |
Expire metadata cache in all Connector plugins.
|
| | | |
|
| | | |
|
| |/
|/| |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If you use the regex feature of Rules/Defaults you may need the real name
of the matched entry in an attribute (for example home of POSIXUser).
You can now enable replace_name for rules or defaults and %{name} will be
replaces in the attribues of the Element before adding them to the target
entry.
This allows you to write something like that in Defaults to assing a default
home directory somewhere else to all users with unset home:
<POSIXUser name='.*' home='/somewhere/%{name}'/>
|
|\ \ \
| | | |
| | | | |
Options: Set default values from config, right after adding a new option
|
| |/ / |
|
| | | |
|
| |/
|/|
| |
| |
| | |
Other plugins that also import user generated python source code, may want to use
safe_module_name from TemplateHelper.
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
This is mostly from 257eb0c17 and 16d3e04cb to allow for setting arbitrary
database options since some settings require nested dictionaries, etc.
This got lost during merge from maint into master because of the completely
different Options parsing.
|
|/ |
|
|
|
|
|
|
|
|
|
|
| |
This removes most blanket except: clauses from all plugins, including
the base plugin libraries, and bcfg2-lint. The few that remain should
all be necessary.
Most of the changes were quite minor, but this did require some
restructuring of the CfgPrivateKeyCreator; as a result, the tests for
that module were rewritten.
|
|\
| |
| |
| |
| | |
Conflicts:
src/lib/Bcfg2/Client/__init__.py
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Bundle dependencies are now realized with RequiredBundle and support
inheritance of the modification flag. This requires new client support
and will only work with clients >= 1.4.0pre2.
|
|/ |
|
|\ |
|
| |
| |
| |
| | |
include or extend other files.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
debian/changelog
doc/conf.py
doc/releases/index.txt
doc/server/database.txt
doc/server/plugins/generators/cfg.txt
doc/server/plugins/generators/sslca.txt
man/bcfg2.conf.5
misc/bcfg2-selinux.spec
misc/bcfg2.spec
osx/Makefile
osx/macports/Portfile
schemas/packages.xsd
solaris-ips/MANIFEST.bcfg2-server.header
solaris-ips/MANIFEST.bcfg2.header
solaris-ips/Makefile
solaris-ips/pkginfo.bcfg2
solaris-ips/pkginfo.bcfg2-server
solaris/Makefile
solaris/pkginfo.bcfg2
solaris/pkginfo.bcfg2-server
src/lib/Bcfg2/Client/Client.py
src/lib/Bcfg2/Client/Proxy.py
src/lib/Bcfg2/Client/Tools/APT.py
src/lib/Bcfg2/Client/Tools/Action.py
src/lib/Bcfg2/Client/Tools/SYSV.py
src/lib/Bcfg2/Client/Tools/YUM.py
src/lib/Bcfg2/Client/Tools/__init__.py
src/lib/Bcfg2/Options.py
src/lib/Bcfg2/Reporting/Collector.py
src/lib/Bcfg2/Reporting/templates/base.html
src/lib/Bcfg2/Server/Admin/__init__.py
src/lib/Bcfg2/Server/BuiltinCore.py
src/lib/Bcfg2/Server/Core.py
src/lib/Bcfg2/Server/Plugins/Packages/Apt.py
src/lib/Bcfg2/Server/Plugins/Probes.py
src/lib/Bcfg2/settings.py
src/lib/Bcfg2/version.py
testsuite/Testsrc/Testlib/TestClient/TestTools/Test_init.py
testsuite/Testsrc/test_code_checks.py
|
| | |
| | |
| | |
| | |
| | |
| | | |
Previously pep8/pylint checks were disable for the APT tool because
there were to many errors. This fix the pylint errors and enables the
code style checks.
|
| | |
| | |
| | |
| | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The database name is sometimes a path (SQLite) and sometimes not
(MySQL, PostgreSQL). This introduces a new Option type,
RepositoryMacroOption, that expands <repository> macros without
canonicalizing the path, so SQLite users can use <repository> in their
settings but MySQL users' database name settings will not be destroyed
by path canonicalization.
The unfortunate downside is that SQLite users can't use ~ in their
database name.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes canonicalizing PathOption values when the default value of
a config file-only option is used. It also fixes PathOptions that get
a file-like object instead of a filename string.
|
| | |
| | |
| | |
| | |
| | | |
This cleans up the temporary config files created by the option
parsing unit tests. Courtesy Alexander Sulfrian.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes several cases in which <repository> macros would not be
properly processed: options that are not added to the parser yet when
early options are parsed; and config file options whose default value
is used.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
This quiets down a lot of tests, especially for option parsing.
|
| | | |
|
| | | |
|
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The existing test_bruteforce_decrypt was nondeterministic; in some
cases, the generated ciphertext would be decryptable with one of the
wrong passphrases, which would cause test failure even though it
decrypts to gibberish. This checks that by splitting it into two
tests:
1. Test with an invalid ciphertext, so that EVPError is always raised;
2. Test with valid ciphertext, and check for *either* EVPError or
decrypted plaintext that is not the same as the original plaintext.
|