Lando API has a concept of "subsystems", each of which extend the `Subsystem` class -- a class containing various convenience methods to determine if a subsystem is initialized with the app context and configuration, whether it is ready or not, whether it is healthy or not, and a mechanism for ensuring that the subsystem is ready. This subsystem structure is tied to the Flask app and must be adapted to Django. Some subsystems may need to be dropped altogether (e.g., `lando_ui_subsystem`) or re-implemented in a different way. This is a preliminary list: - logging_subsystem - sentry_subsystem - auth0_subsystem - cache_subsystem - celery_subsystem - db_subsystem - lando_ui_subsystem - phabricator_subsystem - smtp_subsystem - treestatus_subsystem - repo_clone_subsystem
Bug 1870142 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Lando API has a concept of "subsystems", each of which extend the `Subsystem` class -- a class containing various convenience methods to determine if a subsystem is initialized with the app context and configuration, whether it is ready or not, whether it is healthy or not, and a mechanism for ensuring that the subsystem is ready. This subsystem structure is tied to the Flask app and must be adapted to Django. Some subsystems may need to be dropped altogether (e.g., `lando_ui_subsystem`) or re-implemented in a different way. This is a preliminary list: - logging_subsystem - sentry_subsystem - auth0_subsystem (will need a new test to replace tests in `test_health`) - cache_subsystem (replaced by core support in Django) - celery_subsystem (replaced by generic support in Django) - db_subsystem (replaced by core support in Django) - lando_ui_subsystem (deprecated) - phabricator_subsystem (will need a new test to replace tests in `test_health`) - smtp_subsystem (replaced by core support in Django) - treestatus_subsystem - repo_clone_subsystem (may be moved to workers)