| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
YUM: Add options to enable and disable Yum plugins
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Adds two options you can define:
* disabled_plugins: A comma-separated list of plugins to disable
* enabled_plugins: A comma-separated list of plugins to enable
This allows you to run bcfg2 with certain plugins enabled or disabled
when they're not set that way in the yum configuration. This is
useful because the Bcfg2 YUM plugin is initialized before it can read
in any files that might overwrite yum plugin configuration.
|
|\ \
| | |
| | | |
Client/Proxy: use keyword arguments to match the correct order
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
The XMLRPCTransport __init__ method defines several arguments with default
values. The current call missed the use_datetime argument, so that the
client_timeout will set the use_datetime paramenter and the protocol option
was used as timeout (does not work, because a float is required and raises
an exception).
|
| |
| |
| |
| | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | |
|
| |
| |
| |
| |
| | |
If hard code the default value in your configuration file, it will not change
if the default value will change in the code.
|
| |
| |
| |
| |
| | |
The option was there in bcfg2-1.3.x and is still documented (maybe it just
got lost during the options rewrite).
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
When using altsrc the name of real file created on the client is now
in the realname attribute of the entry. The <Path> filter in the info.xml
should match theses if available to set different permissions for
the different files created by one template with altsrc.
|
|\ \
| | |
| | | |
Options/Commmon: remove default values for ssl-key/ssl-cert
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With these default values it is impossible to remove the ssl key and ssl cert
from the configuration and use password auth. Configuration options could not
be condensed in Bcfg2.Options.Common, because Server and Client needs
different default values.
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Tools/Action: fix typo
|
| | | |
|
|\ \ \ |
|
| |/ / |
|
|\ \ \ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This plugin was developed for 1.3.x and during the transition to master
the changed arguments of Collection.__init__ were missed.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The test uses both variants: get_decisions and get_decision. So there is
no way to fix the code without fixing the test.
|
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Modified from github #204. Thanks to Alexander Sulfrain.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|\ \ \
| | | |
| | | | |
doc: replace tabs with spaces
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Fix doc errors
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
There should be at least two spaces between the option and the description.
|
| |/ / |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | | |
The first version matched Bcfg2-1.3.4.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This removes the ndiff, which is a bit extraneous and can cause up to 30 second
timeouts on larger files with many changes. unified_diff is faster and
generally more applicable, and is already what is shown to the admin on
interactive mode. This can save up to 30 seconds per file, per run.
A future commit can take the resulting unified diff and recreate the ndiff
specifically for the reporting if that is desired.
|
|\ \ \
| | | |
| | | | |
Add only important flag
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Add support for displaying the skipped entries in dryrun mode when using
the --only-important command line flag.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add the new --only-important (-i) command line option. With this option
bcfg2 will only configure the important entries and exits clean
afterwards.
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The interaction entries have a isstale() method, we do not need a
template tag, that tries to figure out this on its own. The isstale()
method works even better: It knows, if the interaction is the current
interaction and compares the timestamp to the current time or (if it is
not the current one) it compares the timestamp to the timestamp of the
next interaction. So using the method of the model, you can browse the
interaction history and see, if the host was stale some time in the
past. Previously all interactions more than 24h ago were marked stale.
|
| | |
| | |
| | |
| | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|/ /
| |
| |
| |
| | |
The condition of the if should match the case, if the entry should be
skipped.
|
| |
| |
| |
| |
| |
| |
| | |
This changes makes the default value match what is specified by the
documentation.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|