Normalize the configuration of VaultBackend and cooker
- Ensure every service for which an (remote or local) access is needed uses the same config structure (dict with 'cls' and 'args' keys). - Extract instanciation (thus confguration) of remote/external services (storage, cache, scheduler) from the VaultBackend constructor; these are now passed as __init__ arguments; their instanciation/configuration is thus now handled by swh.vault.api.server and swh.vault.cooker.get_cooker (with some support in swh.vault.get_vault).
parent
f4ad9690
This commit is part of merge request !37. Comments created here will be created in the context of that merge request.
Showing
- swh/vault/__init__.py 14 additions, 4 deletionsswh/vault/__init__.py
- swh/vault/api/client.py 2 additions, 2 deletionsswh/vault/api/client.py
- swh/vault/backend.py 13 additions, 21 deletionsswh/vault/backend.py
- swh/vault/cache.py 1 addition, 1 deletionswh/vault/cache.py
- swh/vault/cli.py 13 additions, 54 deletionsswh/vault/cli.py
- swh/vault/cookers/__init__.py 38 additions, 1 deletionswh/vault/cookers/__init__.py
- swh/vault/cookers/base.py 17 additions, 17 deletionsswh/vault/cookers/base.py
- swh/vault/cooking_tasks.py 2 additions, 2 deletionsswh/vault/cooking_tasks.py
Loading
Please register or sign in to comment