| Age | Commit message (Collapse) | Author |
|---|
|
still a bit rough, but makes everything a bit more
readable.
|
|
war on spaguetti! :D
|
|
For #501: write base.checks.ProviderCertChecks
(in eip.checks, though.) Basic functionality is there, merging to
tip. Might have to reopen to implement actual cert ts check.
|
|
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.
|
|
|
|
closes #447
deprecates the use of config files; all options are passed
to openvpn as command line arguments.
|
|
|
|
|
|
|
|
|
|
|
|
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 :)
|
|
|
|
|
|
now we expect spec to be a dict for all the JSONLeapConfig instances.
|
|
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.
|
|
|
|
|
|
test provider-definition dump functions.
refactored the set-temp-to-home methods to setUpClass
separate provider-fetch tests on different testcases (so they actually
call to requests).
|
|
adjusted some loose ends to make tests pass again.
this merge is still half-baked regarding functionality:
I've left in place old Configuration class used by
some tests antialias did on his branch. I plan to merge
that functionality with the more recent JSONConfig
and Spec classes.
Conflicts:
src/leap/base/configuration.py
src/leap/eip/config.py
src/leap/eip/tests/test_config.py
|
|
we still have to move most of those tests to test_baseconfig
|
|
|
|
|
|
(cherry picked from get-definition.json branch)
solve merge conflict since antialias was working in
a version in which baseconfig was still at `configuration` file.
Conflicts:
src/leap/base/configuration.py
|
|
|
|
tests green for load/dump operations on config.
defaults on config spec for LeapServiceProvider should
be outputting a minimal working config for bootstrapping
the connection.
we should be using this config mechanism for other config
operations; but probably we should specify a local_editable flag
for those configs that are only changed by server.
|
|
|
|
an initial attempt at stablishing base classes
for config. we go with a jsonconfig by now, and
will switch to a different storage backend in near
future.
things will surely be broken at this state;
i'm splitting work on different commits.
|
|
handling and tests.
uses the requests library for network interactions and mocks for simulating network states.
|
|
|
|
get-definition.json
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(actually, it's not completely working.
it's missing a fix for the broken qt4 libs
inside virtualenv, which still need manual intervention)
|
