MLIA-825 Make backend installation more generic

Use the backend registry to manage installation routines for different
backends as well. This makes the process more generic and allows us
to move towards plug & play for backends (i.e. there should be no code
changes needed in the general MLIA code to add/support new backends).

Change-Id: Ib7c772ec52b2f4d857c2c9871e44dfff97e9d970

1 files changed, 3 insertions, 5 deletions

diff --git a/src/mlia/backend/manager.py b/src/mlia/backend/manager.py
index d953b2d..5a60f95 100644
--- a/src/mlia/backend/manager.py
+++ b/src/mlia/backend/manager.py
@@ -10,13 +10,11 @@ from pathlib import Path
 from typing import Callable
 
 from mlia.backend.config import BackendType
-from mlia.backend.corstone.install import get_corstone_installations
 from mlia.backend.install import DownloadAndInstall
 from mlia.backend.install import Installation
 from mlia.backend.install import InstallationType
 from mlia.backend.install import InstallFromPath
 from mlia.backend.registry import registry as backend_registry
-from mlia.backend.tosa_checker.install import get_tosa_backend_installation
 from mlia.core.errors import ConfigurationError
 from mlia.core.errors import InternalError
 from mlia.utils.misc import yes
@@ -277,9 +275,9 @@ class DefaultInstallationManager(InstallationManager, InstallationFiltersMixin):
 
 def get_installation_manager(noninteractive: bool = False) -> InstallationManager:
     """Return installation manager."""
-    backends = get_corstone_installations()
-    backends.append(get_tosa_backend_installation())
-
+    backends = [
+        cfg.installation for cfg in backend_registry.items.values() if cfg.installation
+    ]
     return DefaultInstallationManager(backends, noninteractive=noninteractive)