| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Extra debconf entries, are entries that were seen but that are not specified in
the configuration.
|
| |
|
|
|
|
|
|
| |
bcfg2-web will fail without setting a valid time zone in newer django versions. This fix initializes the time zone as utc instead of None, to fix most setups without directly breaking functionality.
[reporting]
TIME_ZONE = <valid_tz>
|
|\ |
|
| |
| |
| |
| |
| |
| | |
django-1.8 deprecated referencing views as strings in the url(), so we
need to import the fallback view and referencing the view function
directly.
|
|/
|
|
| |
unicode in py3.
|
|
|
|
|
| |
When importing packages we should not pollute the global modules
namespace and always import new modules with their package name.
|
| |
|
|
|
|
|
| |
Don't let the client follow symbolic links when changing the owner of a
path.
|
| |
|
|\
| |
| | |
Reporting: Add SELinux entries
|
| |
| |
| |
| | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The backwords compatible syntax was removed in 1.10. The "new" syntax is
available since 11 years [1] and was already available in django 1.0 [2].
> Support for the syntax of {% cycle %} that uses comma-separated
> arguments is removed. [3]
[1]: https://code.djangoproject.com/ticket/208
[2]: https://github.com/django/django/commit/09145d2e5f
[3]: https://docs.djangoproject.com/en/2.0/releases/1.10/#features-removed-in-1-10
|
| |
| |
| |
| |
| |
| |
| |
| | |
Django 1.8 deprecated the multiple TEMPLATE_* settings and introduced a
single TEMPLATES config option. Django 1.10 stopped creating a
backwards-compatible TEMPLATES based on the TEMPLATE_* settings.
(See: https://docs.djangoproject.com/en/1.10/ref/templates/upgrading/#the-templates-settings)
|
| |
| |
| |
| |
| |
| |
| | |
Replace django.shortcuts.render_to_response with django.shortcuts.render
because the context_instance argument was deprecated in django 1.8 and
removed in django 1.10. The render shortcut is available since django
1.3, so we can use it without a version check.
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If the module name contains slashes, python will issue an warning:
> Ldap/config.py:1: RuntimeWarning: Parent module '__Ldap_/root/repo/Ldap/config' not found while handling absolute import
> from Bcfg2.Server.Plugins.Ldap import LdapConnection, LdapQuery
So we simply use the basename without the file extension for the module name.
|
| |
| |
| |
| |
| |
| | |
You can now set arbitrary ldap option for the connection by specifying
a dict with the key and the value. You should use the constants from
python-ldap.
|
| |
| |
| |
| |
| |
| |
| | |
You can now specify the server to connect by either host (and optionally
port) or by specifying the full ldap uri. If you specify host and port
the connection will use the plain (unencrypted) ldap protocol by default.
Only if you specify the port "636", it will use ldaps now.
|
| |
| |
| |
| |
| |
| |
| | |
Using the OnDemandDict removes the results of Ldap queries from the
client_metadata cache. We add a new cache per hostname cache for the
single ldap queries and add a new configuration option to enable
caching until the cache is expired manually via XML-RPC.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
With the CallableDict the LdapQueries will only be executed, if the values
are used.
|
| |
| |
| |
| |
| |
| | |
Add a CallableDict (like OnDemandDict, but without caching the results)
to have a dict-like class, that can be cached with the client metadata
without caching the dynamic values.
|
| |
| |
| |
| | |
Now you can also specify simple values for the OnDemandDict.
|
| |
| |
| |
| | |
The OnDemandDict could be used by different plugins.
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For Python2.4 we need older version of pylint and pep8, that finds some
more errors:
- On python2.4 _ast is not available and pylint uses compiler.ast, that
seems to have some problems with the line numbers if a comment is
following the pylint disable marker.
- In python2.4 there is no xml.etree. But we can ignore this error because
Client.XML tries to find a suitable library.
- Some small formatting issues.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
add-missing-reporting-entries
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | |
| | | |
| | | |
| | | | |
It wasn't included in the transition from a wildcard import in 255faaf.
|
|/ / /
| | |
| | |
| | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|\ \ \
| | | |
| | | | |
Reporting/Storage: Import ServiceEntry
|
| |/ /
| | |
| | |
| | | |
It wasn't included in the transition from a wildcard import in 255faaf.
|
|/ /
| |
| |
| |
| |
| | |
This line brakes django detection for the Probes! It resets the global
variable just after the detection. This line was left while changing
the placement of the detection in fa0d86aba32c40d829f9f94411403221a48283e8.
|
|/
|
|
|
| |
It seems to be, that there must not be any Python statement before the
magic comment.
|
| |
|
|\
| |
| | |
Options: Missing config file is not a fatal error
|
| |
| |
| |
| |
| | |
If the config file is not available, it should not be a fatal error,
but bcfg2 should just use the default config values.
|
|\ \
| | |
| | | |
Fix multiline scripts in bcfg2-info debug mode
|
| | | |
|
|/ /
| |
| |
| | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|