Is your feature request related to a problem?
Currently the integrations catalog (repository) is expected to reside inside the dashboards-observavility repo.
This is very limiting for the following reasons :
Hard to test integrations without actually cloning and updating the dashboards-observavility repo.
The dashboards-observavility repo is not the content storage but mostly the infrastructure that enables the integration content to be loaded and displayed
Users may want to load different integration catalog from various sources and not be bounded to one catalog
A Simplified development of an integration would consist of a private integration content repo that is loaded to the integration catalog in a simple manner without needing to change any code inside the OpenSearch project
What solution would you like?
Extend the concept of the integration-repository object to be able to store a list if catalogs
Each catalog may be loaded from various locations including
YANG-DB
commented
1 year ago
Is your feature request related to a problem? Currently the integrations catalog (repository) is expected to reside inside the dashboards-observavility repo. This is very limiting for the following reasons :
What solution would you like?
Do you have any additional context?