Avoid the need to setup the resolver at Manager instantiation, thereby...

Avoid the need to setup the resolver at Manager instantiation, thereby avoiding hitting the cbng-web service for each Python invocation.

assigned to @mihostet

This change means that we don't need to hit cbng-web for each Python startup - we can determine upfront if the environment has been resolved, and only if it hasn't do we need a resolver.

This fixes an immediate issue whereby cbng-web is currently down. cc @mihostet

Tests are failing because we rely on cbng-web for them. !45 (closed) fixes this issue (but that still depends on artifactory.cern.ch I think - though perhaps that has been abstracted away)

added 1 commit

• 72412b90 - Ensure that we maintain the behaviour where it is possible to register a...

Compare with previous version

added 1 commit

• ab13717e - Ensure that we maintain the behaviour where it is possible to register a...

Compare with previous version

added 1 commit

• 4085a2cb - Improve the implementation to provide consistency with the existing implementation.

Compare with previous version

added 1 commit

• f3c29107 - Clarify the difference between Manager.is_installed and Manager.is_registered.

Compare with previous version

added 1 commit

• 84e2198a - Come full circle and restore the original constructor code.

Compare with previous version

added 1 commit

• 3f0ee5f4 - Come full circle and restore the original constructor code.

Compare with previous version

added 1 commit

• f99848a6 - Come full circle and restore the original constructor code.

Compare with previous version

added 1 commit

• 504a7124 - Tidy up the is_resolved method.

Compare with previous version

added 1 commit

• 393433b3 - Correct the use of is_installed, and add a test to confirm that the...

Compare with previous version

added 1 commit

• 8f5a8f31 - Correct the use of is_installed, and add a test to confirm that the...

Compare with previous version

resolved all threads

mentioned in commit d777ac1e

merged