gmartins/separate_data_and_connectivity_options
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [Yes]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Updates description?
Cases
- DATA_PARTITION_MODE="single" and DATA_CONNECTIVITY_MODE="osdu": Need db-connection option or POSTGRESQL_CONN_STRING environment variable;
- DATA_PARTITION_MODE="single" and DATA_CONNECTIVITY_MODE="standalone": Just like above (getting mainRepo);
- DATA_PARTITION_MODE="multiple" and DATA_CONNECTIVITY_MODE="osdu": keep getting osdu repos and the id comes from handshake (same previous behavior)
- DATA_PARTITION_MODE="multiple" and DATA_CONNECTIVITY_MODE="standalone": requires "data-partition-id" option on start or "DATA_PARTITION_ID" environment var, keeps consulting osdu repos with data partition id though.