Age | Commit message (Collapse) | Author |
|
and type casting.
|
|
and a jsonvalidate function too,
that calls to jsonchemea.validate(self, data) with self.schema
We're using the specs to both purposes now:
* providing a type casting system for our config options (work in
progress for the type casting)
* json schema validation
|
|
(was taking the one for eip-service)
also correct the path (should be in root leap config folder).
|
|
config instead of get_config()
|
|
Close #604
|
|
|
|
|
|
Conflicts:
src/leap/app.py
|
|
|
|
|
|
|
|
|
|
|
|
|
|
still fragile; sometimes the qt app inits faster and make the send
command miss the not yet created managemente socket.
|
|
Closes #534. accepts int [1-6] that get passed to openvpn invocation.
We should filter out the polling "state"/"status" commands from the log if
we want it to be real useful.
|
|
|
|
|
|
so it can be more easily moved to base.checks and reused
when eip is a module.
|
|
|
|
|
|
ping the listed gateway.
|
|
|
|
forgot to update eipconnection tests after #504 changes :(
|
|
|
|
documentation of the Exception Hierarchy and attributes.
also a bit of general cleanup around error handling in conductor.
Hopefully to be polished an abstracted to leap.base with time.
not all errors are converted (and the old with_errors/ignoring
errors) are still there, but we should be using this style of handlers
from now on.
wrapping up with this pseudo-feature for now. as we work on individual
features we can mimick the exceptions that are working.
|
|
idea is that we define user messages in the exceptions,
and queue them during (conductor) checks.
user facing dialogs get constucted from exception attrs.
if critical, log as such and exit.
|
|
|
|
It is really dangerous to mess with expanduser paths in tests
without deriving testcases from LeapTestCase.
It'd be good to devise a way of checking for that :(
|
|
stubbing out the timestamp validity check (waiting for #507)
also some more deep tests are missing, wrote todo in tests.
|
|
|
|
implementing a https server with its own base testcase
for convenience. https is delicate, and I think it's better
checking against a real implementation than mocking everything
here.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
it was not updating config dict
|
|
now callables are allowed in specs *only at one level depth*
to allow for last-minute evaluation on context-sensitive data,
like paths affected by os.environ
also some minor modifications to make check tests pass after
putting the new jsonconfig-based eipconfig in place.
aaaaaall green again :)
|
|
|
|
also:
- changed name EIPChecker -> EipConfigChecker
- Added class documentation
|
|
removed "configuration" object. checks are called from conductor.
|
|
|
|
completed first version of EIPChecks
|
|
deprecated base:test_config.test_complete_file (dup functionality)
|
|
plus a little bit of cleaning around (created constants file).
added some notes about inminent deprecation *work in progress*
|
|
will handle pre-init sanity checks for eip connection.
some of this will actually end in more general leap-checks,
but let's keep it alltogether by now.
|
|
|
|
fix tests by introducing a (dirtish) workaround for
check for openvpn keys during vpn connection initialization.
noted that eipconnection constructor should be better not
having that class of side-effects.
|