add correlation id to response header

added 5 commits

• e91c3337...915c66a5 - 4 commits from branch master
• cd7c71f6 - Merge branch 'master' of...

Compare with previous version

@ajoshi19 @njain5 Rebased this MR. Please review and approve.

approved this merge request

added 3 commits

• cd7c71f6...b77fb3c8 - 2 commits from branch master
• b5c366c8 - Merge branch 'master' of...

Compare with previous version

@nthakur Can you please review and approve this MR. Rebased with master.

added 1 commit

• 53db1899 - reverting change from other providers

Compare with previous version

@aliaksandr_ramanovich @rostislav.dublin The trusted pipeline is failing at the **osdu-gcp-deploy ** step. Can you please take a look? Thanks!

@LPereira14 you brought the IndexFilter in the core part and its namesake has been implemented in the GCP space before. So it is a classic conflict as we can see in the log:

...BeanDefinitionStoreException: Failed to parse configuration class [org.opengroup.osdu.indexer.IndexerGcpApplication]; nested exception is org.springframework.context.annotation.ConflictingBeanDefinitionException: Annotation-specified bean name 'indexFilter' for bean class [org.opengroup.osdu.indexer.util.IndexFilter] conflicts with existing, non-compatible bean definition of same name and class [org.opengroup.osdu.indexer.middleware.IndexFilter]...

Pls reconcile them in any of the known ways

cc: @aliaksandr_ramanovich @Rustam_Lotsmanenko

added 3 commits

• 892bbcc4 - Merge branch 'master' of...
• 8a29bfd8 - resolving namespace conflict with gcp
• a475c5fb - Merge branch 'correlation_id' of...

Compare with previous version

requested review from @spellikoduku

@rostislav.dublin Thank you for helping with the error log. I have renamed the namespace for the new Filter I added in core. The pipeline is green now [https://community.opengroup.org/osdu/platform/system/indexer-service/-/pipelines/36907]. Can you please take a look and approve this MR if it looks good ?

approved this merge request

approved this merge request

Merging as trusted build is green

merged

mentioned in commit d7a937a2

@rostislav.dublin Thank you for your approval. FYI - We have merged this MR with master that triggered a build but there is a failing osdu-gcp-test that may need your attention.

@LPereira14 thank you for the notice. I checked it again by rerunning the pipeline on the "master" branch and it showed 5 tests failed. Probably it was caused by some temporary slow downing of ES performance, we saw many "index not created after waiting for 140 seconds" occurrences there in logs. Then I reran it again (after 1 hour timeout) - and GCP-tests completed smooth. So you can be sure for your MR, it is able to have all tests "green".

cc: @Rustam_Lotsmanenko @Oleksandr_Kosse

@rostislav.dublin Thank you for the confirmation.

added Common Code label