ipsilon.git/ipsilon/util, branch log_location

Add source code context information to debug log messages

2015-01-21T19:04:12+00:00

The log.debug() function helpfully adds the name of the function
invoking it but in a complicated software package there are many
functions/methods which share the same name. Thus a debug message lke
this:

DEBUG(__init__): xxx

does not give you much context, there are probably hundreds of
__init__ methods. It would help to qualify the method name which it's
class name, that gives a lot more context when reading the
log. Sometimes it's also helpful to know the file and line number.

This patch adds the class name to the function and included the
filename and line number as well. The file path is trimmed to the last
3 components, sufficient to give context but not too verbose. Now the
debug message might look like this instead:

DEBUG(ipsilon/providers/common.py:129 LoadProviders.__init__()): xxx

Also included is a config option 'stacktrace_on_error' which will
include a stacktrace when the log.error function is called. It can be
very useful to see a stacktrace when logging an error, it defaults to
off.

Signed-off-by: John Dennis

Fix file permissions and remove shebang's

2014-12-16T15:51:43+00:00

Signed-off-by: Patrick Uiterwijk 
Reviewed-by: Simo Sorce

Add defaults to List objects

2014-12-05T20:44:06+00:00

Otherwise we get backtraces when checking for list members and no configuration
have been stored in the database yet.

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk

Allow to pass drectly a URL to the Store class

2014-12-05T19:49:30+00:00

This is useful for plugins that want to use their own database configuration
but still want to reuse he Store class for simplicity.

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk

Return proper errors if config is read-only

2014-11-12T22:47:39+00:00

Do not throw 501 errors, instead return warnings that the configuration
changes cannot be applied.

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk

Add option to source configuration from a file

2014-11-12T22:47:36+00:00

If the configfile:// schema is used, the data is sourced from an ini
style config file instead of being read from a database.

The tables in this data source will be considered read-only and
all modification functions will throw exceptions.

Only 2 and 3 columns tables are supported, and the first column
values must not contain spaces (typically a name/identifier).

The adminconfig db is the only supported one at this time.

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk

Remove unused option

2014-11-12T22:47:34+00:00

Autotable is always enabled, so remove the option and just alays use it.

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk

Make internal functions private

2014-11-12T22:47:31+00:00

load_data and reset_data are used only internally,
turn them into private functions

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk

Remove unused function

2014-11-12T22:47:27+00:00

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk

Refactor plugin initialization and enablement

2014-11-12T22:47:25+00:00

Move most plugin enablement and initialization code in plugin.py to
reduce code duplication and simplify and unifify plugin enablement
for all base plugin types (login, info, providers).

This patch breaks backwards compatibility as it changes how the list
of enabled plugins is stored in the database tables.

Signed-off-by: Simo Sorce 
Reviewed-by: Patrick Uiterwijk