Search merge requestshttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests2024-01-09T13:13:16Zhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/556move optimized geoquery builder to core2024-01-09T13:13:16ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.commove optimized geoquery builder to coreIssue: https://gitlab.opengroup.org/osdu/pmc/community-implementation/-/issues/20
In the Search service, there is duplicated code for building Elasticsearch queries present in CSP modules. This MR refactors Geo query building, moving it...Issue: https://gitlab.opengroup.org/osdu/pmc/community-implementation/-/issues/20
In the Search service, there is duplicated code for building Elasticsearch queries present in CSP modules. This MR refactors Geo query building, moving it to the Core, Azure version is used as a sample.
## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [x] AWS
- [x] Azure
- [x] Google Cloud
- [x] IBM
- [x] Common code
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Code for Geo query building duplicated (with differences) in each CSP module.
## What is the new/expected behavior?
Code for Geo query building extracted to the core, Azure optimized query builder is used.
## Have you added/updated Unit Tests and Integration Tests?
Yes
## Any other useful informationM21 - Release 0.24Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/612reduce the group cache timeout to 30s2024-01-09T02:02:02ZNeelesh Thakurreduce the group cache timeout to 30s## Type of change
- [ ] Bug Fix
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [X] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
Reduce the...## Type of change
- [ ] Bug Fix
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [X] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
Reduce the group cache TTL to 30s. Currently it's set to 1hr, which is very long time. Record with newly created group/ACL won't be searchable for 1hr. This change also makes this TTL consistent with Storage service cache configuration.M23 - Release 0.26Neelesh ThakurChad LeongNeelesh Thakurhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/613Upgrade core-lib-ibm version2024-01-05T08:45:45ZAshwani PandeyUpgrade core-lib-ibm versionhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/610https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/610M22 - Release 0.25Ashwani PandeyAshwani Pandeyhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/610ibm-lib version upgrade2024-01-05T08:37:10ZAshwani Pandeyibm-lib version upgradecore-lib-ibm version upgrade to 0.25.1core-lib-ibm version upgrade to 0.25.1M22 - Release 0.25Ashwani PandeyAshwani Pandeyhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/611[MSCOSDU-1894] fix json-smart vulnerability2024-01-03T07:24:23ZVidyaDharani Lokam[MSCOSDU-1894] fix json-smart vulnerability* upgraded `json-smart` to `2.5.0` to remediate vulnerability.
* upgraded `reactor-netty` to `1.1.14`.* upgraded `json-smart` to `2.5.0` to remediate vulnerability.
* upgraded `reactor-netty` to `1.1.14`.M23 - Release 0.26VidyaDharani LokamVidyaDharani Lokamhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/600[MSCOSDU-1866] fix io.netty, reactor-netty-http vulnerabilities2024-01-01T07:24:06ZVidyaDharani Lokam[MSCOSDU-1866] fix io.netty, reactor-netty-http vulnerabilities# Change details
* upgraded `core-lib-azure` to `0.25.0-rc2`
* upgrade `io.netty:netty-bom` version to `4.1.101.Final`
* upgrade `reactor-netty-http` version to `1.1.13`
# Changes in:
* [ ] GCP
* [x] Azure
* [ ] AWS
* [ ] IBM# Change details
* upgraded `core-lib-azure` to `0.25.0-rc2`
* upgrade `io.netty:netty-bom` version to `4.1.101.Final`
* upgrade `reactor-netty-http` version to `1.1.13`
# Changes in:
* [ ] GCP
* [x] Azure
* [ ] AWS
* [ ] IBMM22 - Release 0.25VidyaDharani LokamVidyaDharani Lokamhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/606Gonrg 8958 disable policy2023-12-28T13:28:26ZSiarhei Poliak [EPAM / GCP]Gonrg 8958 disable policy## Type of change
- [-] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provi...## Type of change
- [-] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [-] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Policy enabled
## What is the new/expected behavior?
Policy disabled
## Have you added/updated Unit Tests and Integration Tests?
no
## Any other useful informationM23 - Release 0.26https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/605Cherry-pick 'adding note in tutorial regarding indexer feature flag for AsIng...2023-12-19T08:45:54ZChad LeongCherry-pick 'adding note in tutorial regarding indexer feature flag for AsIngestedCoordinates' into release/0.25**Original MR**: !597
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporati...**Original MR**: !597
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/system/search-service/-/pipelines/new?ref=cherry-pick-for-597)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/597adding note in tutorial regarding indexer feature flag for AsIngestedCoordinates2023-12-19T08:31:00ZMark Chanceadding note in tutorial regarding indexer feature flag for AsIngestedCoordinates## Type of change
* [ ] Bug Fix
* [x] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- \[NO\]
## Does this introduce a change in the cloud prov...## Type of change
* [ ] Bug Fix
* [x] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- \[NO\]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
* [ ] AWS
* [ ] Azure
* [ ] Google Cloud
* [ ] IBM
## Does this introduce a breaking change?
- \[NO\]
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM22 - Release 0.25https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/604Cherry-pick 'Update tutorial about keywordLower feature' into release/0.252023-12-18T16:58:26ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Update tutorial about keywordLower feature' into release/0.25**Original MR**: !593
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporati...**Original MR**: !593
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/system/search-service/-/pipelines/new?ref=cherry-pick-for-593)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/593Update tutorial about keywordLower feature2023-12-18T16:38:01ZStanisław BienieckiUpdate tutorial about keywordLower feature## Type of change
- [X] Tutorial update
Tutorial update to reflect indexer MR and ADR
https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/112
https://community.opengroup.org/osdu/platform/system/indexer-service...## Type of change
- [X] Tutorial update
Tutorial update to reflect indexer MR and ADR
https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/112
https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/618/M22 - Release 0.25https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/590Changed HealhCheckApi (GONRG-8979)2023-12-18T15:03:22ZRiabokon Stanislav(EPAM)[GCP]Changed HealhCheckApi (GONRG-8979)## Type of change
- [ ] Bug Fix
- [x] 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?
- [x] AWS
- [x] Azure
- [x] Google Clou...## Type of change
- [ ] Bug Fix
- [x] 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?
- [x] AWS
- [x] Azure
- [x] Google Cloud
- [x] IBM
## Does this introduce a breaking change?
- [YES/NO]
## What is the new/expected behavior?
Updated openapi.xml, added int tests, and removed outdated code for HealthApi.M23 - Release 0.26Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/603Cherry-pick 'Full Upgrade of First Party Library Dependencies for Release 0.2...2023-12-14T10:21:23ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Full Upgrade of First Party Library Dependencies for Release 0.25' into release/0.25**Original MR**: !602
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporati...**Original MR**: !602
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/system/search-service/-/pipelines/new?ref=cherry-pick-for-602)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/602Full Upgrade of First Party Library Dependencies for Release 0.252023-12-13T18:52:40ZDavid Diederichd.diederich@opengroup.orgFull Upgrade of First Party Library Dependencies for Release 0.25This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to try to fully upgrade all dependent libraries to see if the latest code will work.
It is expected that these will ...This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to try to fully upgrade all dependent libraries to see if the latest code will work.
It is expected that these will often fail, since the upgrades were previously rejected for failing pipelines and have not been directly addressed yet.
This upgrade should only be merged in the CI pipeline reports success.
If this MR has failed, we can spend a little time investigating to see if a trivial upgrade could achieve compatiblity to the new library.
But significant upgrade efforts should not occur on this MR, as part of the release tagging process.
Instead, significant work should be scheduled for a subsequent milestone.
This MR may co-exist with a separate, smaller upgrade MR.
If both pass, this one should be used instead.
### Dependency Information Before the Upgrade
```
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Branch: master
SHA: 2bb7cb20ff73c74475032fba5d9e19bda5a460de
Maven: 0.26.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| ------------------------------------------------------------------------- | ---------- | -------------------------- |
| core-lib-azure | 0.25.0-rc2 | 0.24.0 |
| core-lib-gc | 0.24.0 | |
| os-core-lib-aws | 0.25.0-rc3 | 0.25.0-rc3 |
| os-core-common | 0.25.0-rc2 | 0.25.0-rc2 |
| os-core-lib-ibm | 0.24.0 | 0.24.0 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.17.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.17.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2, 2.20.0 |
| (3rd Party) org.elasticsearch.client.elasticsearch-rest-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.client.elasticsearch-rest-high-level-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-cli | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-core | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-geo | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-lz4 | | 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-plugin-classloader | | 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-secure-sm | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-x-content | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.aggs-matrix-stats-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.lang-mustache-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.mapper-extras-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.parent-join-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.rank-eval-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.26, 1.33, 1.27, 2.0 |
### Dependency Information After the Upgrade
```
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Branch: dependency-upgrade
SHA: 70b6e4ed7af0fae1e282ef5cf2beac3f18ae2dea
Maven: 0.26.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| ------------------------------------------------------------------------- | ------ | -------------------------- |
| core-lib-azure | 0.25.0 | 0.25.0 |
| core-lib-gc | 0.25.0 | |
| os-core-lib-aws | 0.25.0 | 0.25.0 |
| os-core-common | 0.25.0 | 0.25.0 |
| os-core-lib-ibm | 0.25.0 | 0.25.0 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.17.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.17.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2, 2.20.0 |
| (3rd Party) org.elasticsearch.client.elasticsearch-rest-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.client.elasticsearch-rest-high-level-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-cli | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-core | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-geo | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-lz4 | | 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-plugin-classloader | | 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-secure-sm | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-x-content | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.aggs-matrix-stats-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.lang-mustache-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.mapper-extras-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.parent-join-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.rank-eval-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.26, 1.33, 1.27, 2.0 |M22 - Release 0.25https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/601Cherry-pick '[MSCOSDU-1866] fix json, io.netty, reactor-netty-http vulnerabil...2023-12-12T10:21:16ZDavid Diederichd.diederich@opengroup.orgCherry-pick '[MSCOSDU-1866] fix json, io.netty, reactor-netty-http vulnerabilities' into release/0.25**Original MR**: !600
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporati...**Original MR**: !600
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/system/search-service/-/pipelines/new?ref=cherry-pick-for-600)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/599Remove SNAPSHOT dependencies2023-12-09T01:53:39ZDavid Diederichd.diederich@opengroup.orgRemove SNAPSHOT dependenciesThis automated MR removes usage of `SNAPSHOT` versions in the first party library dependencies.
Since `SNAPSHOT` dependencies change frequently -- by their nature -- usage of them across projects is dangerous and should be avoided.
### ...This automated MR removes usage of `SNAPSHOT` versions in the first party library dependencies.
Since `SNAPSHOT` dependencies change frequently -- by their nature -- usage of them across projects is dangerous and should be avoided.
### Dependency Information Before the Upgrade
```
Branch: master
SHA: 926b3b39b89b1952c8e5e67eaadf67a0c1754f4f
Maven: 0.25.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| ------------------------------------------------------------------------- | --------------- | -------------------------- |
| core-lib-azure | 0.24.0 | 0.24.0 |
| core-lib-gc | 0.24.0 | |
| os-core-lib-aws | 0.25.0-SNAPSHOT | 0.25.0-SNAPSHOT |
| os-core-common | 0.25.0-rc2 | 0.25.0-rc2 |
| os-core-lib-ibm | 0.24.0 | 0.24.0 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.17.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.17.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2, 2.20.0 |
| (3rd Party) org.elasticsearch.client.elasticsearch-rest-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.client.elasticsearch-rest-high-level-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-cli | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-core | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-geo | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-lz4 | | 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-plugin-classloader | | 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-secure-sm | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-x-content | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.aggs-matrix-stats-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.lang-mustache-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.mapper-extras-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.parent-join-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.rank-eval-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.26, 1.33, 1.27, 2.0 |
### Dependency Information After the Upgrade
```
Branch: snapshot-removal
SHA: c0bc4aa47409bf44e2a3def28c49ed4b9b2bbda8
Maven: 0.25.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| ------------------------------------------------------------------------- | ---------- | -------------------------- |
| core-lib-azure | 0.24.0 | 0.24.0 |
| core-lib-gc | 0.24.0 | |
| os-core-lib-aws | 0.25.0-rc3 | 0.25.0-rc3 |
| os-core-common | 0.25.0-rc2 | 0.25.0-rc2 |
| os-core-lib-ibm | 0.24.0 | 0.24.0 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.17.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.17.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2, 2.20.0 |
| (3rd Party) org.elasticsearch.client.elasticsearch-rest-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.client.elasticsearch-rest-high-level-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-cli | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-core | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-geo | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-lz4 | | 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-plugin-classloader | | 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-secure-sm | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.elasticsearch-x-content | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.aggs-matrix-stats-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.lang-mustache-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.mapper-extras-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.parent-join-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.elasticsearch.plugin.rank-eval-client | 7.8.1 | 7.8.1, 7.17.15 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.26, 1.33, 1.27, 2.0 |M22 - Release 0.25https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/598Changes made to fix S360 vulnerability2023-12-08T21:20:16ZVaibhavi KamaniChanges made to fix S360 vulnerability## Type of change
- [ ] Bug Fix
- [ ] Feature
- [x] S360 Vulnerability
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
## Does this introduc...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [x] S360 Vulnerability
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [x] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]Vaibhavi KamaniVaibhavi Kamanihttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/591retry in send method fixed for azure and added some logs2023-12-07T16:35:27ZHarshika Dhootretry in send method fixed for azure and added some logs## Does this introduce a change in the core logic?
- [YES/NO] no
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [X] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a brea...## Does this introduce a change in the core logic?
- [YES/NO] no
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [X] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [YES/NO]no
Adding logs such that for any 4xx or 5xx calls we are able to trace the flow using correlation id, urls, http methods, which will enable us to perform the debugging faster and also at the places where we are blocked because of no correlation id
PR master pipeline: [https://community.opengroup.org/osdu/platform/system/search-service/-/pipelines/229566](https://community.opengroup.org/osdu/platform/system/search-service/-/pipelines/229566)
parity Master pipeline without my changes: [https://community.opengroup.org/osdu/platform/system/search-service/-/pipelines/229581](https://community.opengroup.org/osdu/platform/system/search-service/-/pipelines/229581)
Azure m18 PR :[https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/574](https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/574)
Task ID: 31325M22 - Release 0.25Harshika DhootHarshika Dhoothttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/595update os-core-common in testing projects2023-12-07T13:22:03ZSolomon Ayalewupdate os-core-common in testing projects## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provi...## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM22 - Release 0.25https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/594update os-core-lib-aws version2023-12-05T23:46:40ZYunhua Koglinupdate os-core-lib-aws version## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provi...## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [x] AWS
- [ ] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM22 - Release 0.25Yunhua KoglinYunhua Koglin