Manage state of not configured retrieval
Goal
We want to distinguish a managed DLE instance and not start the data refresh process until the DLE instance is configured.
TODO / How to implement
The idea is to create a special marker to detect whether DLE runs in clouds (from any marketplace) environment and it has not been configured yet
Such a marketplace marker is going to be a file (for example, pending.retrieval
) that creates automatically during initialization and store to the metadata directory by installation script.
The retrieval refreshing is not running if this file is exist
A new status (pending
) is added for the retrieval service, which signals that the engine is managed by Marketplace and has not been configured yet:
-
the UI should redirect user after login to the configuration page (or tab) by default if retrieval is
pending
-
the
pending
becomes the default status for Marketplace installations RunningPOST /admin/config
, DLE removes thepending.retrieval
file: -
if the file is exist
-
if config is valid
Marketplace scenario:
- create a file (
pending.retrieval
) in the metadata directory - use
dle_cf_template.yaml
to prepare this file before running DLE
Acceptance criteria
- not to start the data refresh process until the managed DLE instance is configured
- configuration page is auto-presented to admin in UI if retrieval jobs have not been configured