| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
If required the DBSettings config hook will call django.setup right after
configuring django with the required settings. So we can drop the calls to
django.setup from all other places.
|
| |\
| |
| | |
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.
|
| |/
|
|
|
| |
bcfg2-reports does not call sync_databases or migrate_databases before
making the database queries. So we need to initialize django here, too.
|
| |
|
|
|
| |
All bcfg2-reports subcommands, that work with specific interactions, can
now ignore interactions created by --dry-run or --only-important run.
|
| | |
|
| |
|
|
|
|
| |
Add a new column "stale", that displays if a host is stale or not. It could be
determined by parsing the date column, but it would be more convenient to
have a separate column for that.
|
| |
|
