| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
You can add now a list of aliases to a Subcommand to make it available with
different names. Each alias in the list is used without modification,
especially the aliases do not get converted to lower case (this is for example
required for "EOF").
|
| |
|
|
|
|
|
| |
The expirecache subcommand is only usefull from an interactive shell, so
do not advertise it in the help from the commandline.
|
|
|
|
| |
The expirecache subcommand was using an old API.
|
|
|
|
|
|
|
| |
Some subcommands only makes sense, if they are called from an interactive
shell and to interface a running server. Now we can mark a Subcommand
as only_interactive and it will not be callable as argument from the command
line.
|
| |
|
|
|
|
|
|
| |
We change the parser namespace so contain all the global flags. So we silently
erase the parser cache and have to set the parsed flag, so that the Parser
does not use our "empty" new namespace as cached result.
|
|
|
|
|
|
|
| |
Expirecache is now part of bcfg2-admin and will call expire_metadata_cache
from Core via XML-RPC. This will expire the metadata cache of the supplied
clients (or the complete cache if no arguments are supplied) on a running
bcfg2-server.
|
|\
| |
| | |
Reporting: Do not fail, if no interactions found
|
| |
| |
| |
| |
| |
| | |
With the filter feature of bcfg2-reports it is possible that all
interactions of a client gets filtered. Now we simply skip those clients
without interactions and do not fail with an exception.
|
|\ \
| | |
| | | |
Expire metadata cache in all Connector plugins.
|
| | |
| | |
| | |
| | |
| | |
| | | |
The data returned by Connector.get_additional_data is also cached, so the
plugin needs to invalidate the caches, even if it does not implement
Connector.get_additional_groups.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
AWSTags cannot know whether the tags change, so it cannot expire the
metadata cache correctly. Instead we have to expire the cache at
beginning of each client run. This practically disables agressive
client metadata caching, so we print a warning.
|
| | |
| | |
| | |
| | | |
This was maybe missing in 38f3cfcfd.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
SSHbase supply the public keyfiles as additional metadata, so we need to
expire the metadata cache if we get an event for such file. We would only
need to expire the metadata cache for hosts, that reference that exact file
(host or group specific) but we cannot get this information, so that we
simply expire the metadata cache for all hosts.
|
| | | |
|
| | | |
|
|\ \ \ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
If we check for the existance of a related object, newer django versions
(>= 1.5) raise a ObjectDoesNotExist exception and we have to handle it.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
bcfg2-reports does not call sync_databases or migrate_databases before
making the database queries. So we need to initialize django here, too.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Django 1.8 introduced different template engines and droped the
get_template_from_string function as it does not support the new feature.
|
| | | |
| | | |
| | | |
| | | | |
The old name was deprecated with django1.6 and removed with django1.8.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The _meta API was changed with django 1.8 and get_fields() now returns all
model fields even fields defined in related models. But while creating the
Entries we use this field list for construction and the list should only
contain local fields.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Django changed the default value for BooleanFields some time ago, so we
add an explicit default value to remove the warnings.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
You could not import a class, that is defined in a function. We need to
return the class, but we do not want to define it multiple times. So we
have to save the class in a global variable.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The private API django.db.backend is deprecated in django 1.7 and removed in
django 1.8, so we use another way to get the DatabaseOperations from the
connection.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Do not use the global django connection object but the matching instance
from the django connections list.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We need to go through the Options parsing before we could use django and
import the models. The Options parsing will setup django and prepare the
required settings.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
django.db.close_connection() is deprecated in django1.7 (and removed in 1.8).
The new django.db.close_old_connections() does not seem to work like the old
one (see http://stackoverflow.com/a/32614137), so we replace it with an own
implementation.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The models should be loaded during the options parsing and so this call
issues a warning message from django, that the models are already
registered.
|
| | | |
| | | |
| | | |
| | | | |
django.setup() is already called from the option parsing before.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
On the first use with django-1.7 we manually get the south migration status
and fake apply the django migration to that point. With that users can switch
to django migrations at any point of time.
The code simply takes the name of the last south migration and forwards the
django migrations to that point. Therefor it is required to keep the names
of the migrations in sync.
It is required to keep the migration names of the two systems in sync.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- reports.wsgi uses get_wsgi_application() now
- old south-based migrations have been moved
- manage.py has been updated
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Add makemigration for django>1.7 or schemamigration for django<=1.6 with south.
|
|\ \ \ \ \ |
|