You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While in the past we created whole new data source types (see: P6), we no longer do that. In order to still allow users access to specific data source types in a quick, plug-and-play format, we need to include some sort of json/yaml file in the DL codebase which will auto-populate some custom sources as data source options when a user first spins up a DeepLynx container.
Design
json or yaml file and some parser on the backend which converts the file into custom source types on container creation. Also a good idea to add to existing containers as blank checkboxes in the data source config list in settings.
Impact
Mostly backend changes. Shouldn't effect the API. Will add an extra thing to do in the background upon container creation.
The text was updated successfully, but these errors were encountered:
Reason
While in the past we created whole new data source types (see: P6), we no longer do that. In order to still allow users access to specific data source types in a quick, plug-and-play format, we need to include some sort of json/yaml file in the DL codebase which will auto-populate some custom sources as data source options when a user first spins up a DeepLynx container.
Design
json or yaml file and some parser on the backend which converts the file into custom source types on container creation. Also a good idea to add to existing containers as blank checkboxes in the data source config list in settings.
Impact
Mostly backend changes. Shouldn't effect the API. Will add an extra thing to do in the background upon container creation.
The text was updated successfully, but these errors were encountered: