Move Search Config out of os-core-common (GONRG-744)
Type of change
-
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
Does this introduce a breaking change?
- [YES]
The breaking change was introduced in os-core-common
The config from common lib does not support search- and indexer-related values. These values were moved to org.opengroup.osdu.indexer.config.IndexerConfigurationProperties
What is the current behavior?
In this ticket the new separate config org.opengroup.osdu.indexer.config.IndexerConfigurationProperties was created. It is managed by @ConfigurationProperties.
All occurrences of the old config were replaced by new config
Have you added/updated Unit Tests and Integration Tests?
- [YES]
Any other useful information
depends on: osdu/platform/system/lib/core/os-core-common!34 (merged) contains changes from: !52 (merged), !51 (merged)
Merge request reports
Activity
mentioned in merge request osdu/platform/system/lib/core/os-core-common!34 (merged)
added GC label
added 7 commits
-
58660584...f2466c1d - 6 commits from branch
master - 542d73b0 - NOTICE update on fossa-check-notice findings
-
58660584...f2466c1d - 6 commits from branch
added 11 commits
-
542d73b0...94792881 - 10 commits from branch
master - 8583e062 - Merge remote-tracking branch 'origin/master' into gcp-search-config-changes
-
542d73b0...94792881 - 10 commits from branch
Hi @igor_filippov pls investigate the error https://community.opengroup.org/osdu/platform/system/indexer-service/-/jobs/120003#L850
We didn't have it on the last 'master' pipeline. So this is definitely something brought by your MR change.
added 1 commit
- 8a9a82da - Set core-common version compatible with IBM testing
mentioned in commit f0699e2a
changed milestone to %M1 - Release 0.1
