Legal merge requestshttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests2024-01-24T23:21:46Zhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/505Use full URL instead of relative path2024-01-24T23:21:46ZLawrence ChanUse full URL instead of relative path## All Submissions:
-------------------------------------
* [YES/NO] I have added an explanation of what changes in this merge do and why we should include it?
* [YES/NO] I have updated the documentation accordingly.
* [YES/NO/NA] I have...## All Submissions:
-------------------------------------
* [YES/NO] I have added an explanation of what changes in this merge do and why we should include it?
* [YES/NO] I have updated the documentation accordingly.
* [YES/NO/NA] I have added tests to cover my changes.
* [YES/NO/NA] All new and existing tests passed.
* [YES/NO/NA] My code follows the code style of this project.
* [YES/NO/NA] I ran lint checks locally prior to submission.
## What is the current behavior?
-------------------------------------
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
Issue: Remember to link the workitem to this pull request.
## What is the new behavior?
-------------------------------------
<!-- Please describe the behavior or changes that are being added by this PR. -->
-
-
-
## Does this introduce a breaking change?
-------------------------------------
- [YES/NO]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Any relevant logs, error output, etc?
-------------------------------------
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
## Other information
-------------------------------------
<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/504Use full URL instead of relative path2024-01-18T15:18:22ZLawrence ChanUse full URL instead of relative path## Change Details
* Issue Reference: https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/68
* added configuration `api.server.fullUrl.enabled` to enable full server url in OpenAPI swagger
* Currently only...## Change Details
* Issue Reference: https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/68
* added configuration `api.server.fullUrl.enabled` to enable full server url in OpenAPI swagger
* Currently only in Azure it is enabled. For Other \[CSP/Common Core\] there is no change.
### Configuration Details
* `api.server.fullUrl.enabled=true` It will generate full server url in the OpenAPI swagger
* `api.server.fullUrl.enabled=false` It will generate only the contextPath only
* Reference: https://springdoc.org/faq.html#_how_is_server_url_generatedM23 - Release 0.26Thulasi Dass SubramanianThulasi Dass Subramanianhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/503Draft: Use full URL instead of relative path2023-12-20T23:57:09ZLawrence ChanDraft: Use full URL instead of relative path## All Submissions:
-------------------------------------
* [YES/NO] I have added an explanation of what changes in this merge do and why we should include it?
* [YES/NO] I have updated the documentation accordingly.
* [YES/NO/NA] I have...## All Submissions:
-------------------------------------
* [YES/NO] I have added an explanation of what changes in this merge do and why we should include it?
* [YES/NO] I have updated the documentation accordingly.
* [YES/NO/NA] I have added tests to cover my changes.
* [YES/NO/NA] All new and existing tests passed.
* [YES/NO/NA] My code follows the code style of this project.
* [YES/NO/NA] I ran lint checks locally prior to submission.
## What is the current behavior?
-------------------------------------
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
Issue: Remember to link the workitem to this pull request.
## What is the new behavior?
-------------------------------------
<!-- Please describe the behavior or changes that are being added by this PR. -->
-
-
-
## Does this introduce a breaking change?
-------------------------------------
- [YES/NO]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Any relevant logs, error output, etc?
-------------------------------------
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
## Other information
-------------------------------------
<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/502Use full URL instead of relative path2023-12-20T23:41:39ZLawrence ChanUse full URL instead of relative path## All Submissions:
-------------------------------------
* [YES/NO] I have added an explanation of what changes in this merge do and why we should include it?
* [YES/NO] I have updated the documentation accordingly.
* [YES/NO/NA] I have...## All Submissions:
-------------------------------------
* [YES/NO] I have added an explanation of what changes in this merge do and why we should include it?
* [YES/NO] I have updated the documentation accordingly.
* [YES/NO/NA] I have added tests to cover my changes.
* [YES/NO/NA] All new and existing tests passed.
* [YES/NO/NA] My code follows the code style of this project.
* [YES/NO/NA] I ran lint checks locally prior to submission.
## What is the current behavior?
-------------------------------------
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
Issue: Remember to link the workitem to this pull request.
## What is the new behavior?
-------------------------------------
<!-- Please describe the behavior or changes that are being added by this PR. -->
-
-
-
## Does this introduce a breaking change?
-------------------------------------
- [YES/NO]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Any relevant logs, error output, etc?
-------------------------------------
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
## Other information
-------------------------------------
<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/501Cherry-pick 'Full Upgrade of First Party Library Dependencies for Release 0.2...2023-12-16T10:26:09ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Full Upgrade of First Party Library Dependencies for Release 0.25' into release/0.25**Original MR**: !500
### 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**: !500
### 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/security-and-compliance/legal/-/pipelines/new?ref=cherry-pick-for-500)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/500Full Upgrade of First Party Library Dependencies for Release 0.252023-12-15T20:02:48ZDavid 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: a968bf3d07a0dd02d9c6356379d6a435311f395d
Maven: 0.26.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------------- | -------------------------- |
| apd-core | 0.24.0-rc1 | |
| core-lib-azure | 0.25.0-rc2 | 0.16.0 |
| core-lib-gc | 0.24.0 | |
| core-plus-common-lib | 0.24.0-rc2 | |
| os-core-lib-aws | 0.25.0-rc2 | 0.25.0-rc2 |
| obm | 0.24.0 | |
| oqm | 0.24.0 | |
| os-core-common | 0.25.0-rc2 | 0.24.0, 0.16.0, 0.25.0-rc2 |
| os-core-lib-ibm | 0.24.0 | 0.24.0 |
| os-obm-core | 0.25.0-rc1 | |
| os-oqm-core | 0.25.0-rc1 | |
| os-osm-core | 0.25.0-rc1 | |
| osm | 0.24.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.0, 2.13.4.2 | 2.13.2.2, 2.10.3 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.17.2, 2.13.3, 2.11.2 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.17.2, 2.11.2, 2.13.3 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 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: 8213504420b5528cc415b39a571b3679a73a91ff
Maven: 0.26.0-SNAPSHOT
```
| Maven Dependencies | testing/ | _Root_ |
| ------------------------------------------------------- | -------------------------- | ------ |
| core-lib-azure | 0.16.0 | |
| os-core-lib-aws | 0.25.0 | |
| os-core-common | 0.25.0, 0.16.0 | 0.25.0 |
| os-core-lib-ibm | 0.25.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2, 2.13.4.1, 2.10.3 | 2.14.0 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.2, 2.13.3, 2.11.2 | 2.17.1 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.13.3 | |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.13.3 | |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.13.3 | |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.2, 2.11.2, 2.13.3 | 2.17.1 |
| (3rd Party) org.yaml.snakeyaml | 1.30, 1.27, 2.0 | 2.0 |M22 - Release 0.25https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/499Cherry-pick '[MSCOSDU-1857] fix json vulnerability' into release/0.252023-12-12T10:21:34ZDavid Diederichd.diederich@opengroup.orgCherry-pick '[MSCOSDU-1857] fix json vulnerability' into release/0.25**Original MR**: !494
### 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**: !494
### 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/security-and-compliance/legal/-/pipelines/new?ref=cherry-pick-for-494)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/498cherry-pick MR 497 from master2023-12-12T12:39:04ZYunhua Koglincherry-pick MR 497 from masterOriginal MR: !497
## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [NA] ...Original MR: !497
## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [NA] I have added tests to cover my changes.
* [YES] All new and existing tests passed.
* [YES] My code follows the code style of this project.
* [YES] I ran lint checks locally prior to submission.
## What is the current behavior?
-------------------------------------
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
Issue: Remember to link the workitem to this pull request.
## What is the new behavior?
-------------------------------------
<!-- Please describe the behavior or changes that are being added by this PR. -->
-
-
-
## Does this introduce a breaking change?
-------------------------------------
- [NO]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Any relevant logs, error output, etc?
-------------------------------------
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
## Other information
-------------------------------------
<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->M22 - Release 0.25Yunhua KoglinYunhua Koglinhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/497disable mongo2023-12-11T18:12:42ZYunhua Koglindisable mongo## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [NA] I have added tests ...## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [NA] I have added tests to cover my changes.
* [YES] All new and existing tests passed.
* [YES] My code follows the code style of this project.
* [YES] I ran lint checks locally prior to submission.
## What is the current behavior?
-------------------------------------
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
Issue: Remember to link the workitem to this pull request.
## What is the new behavior?
-------------------------------------
<!-- Please describe the behavior or changes that are being added by this PR. -->
-
-
-
## Does this introduce a breaking change?
-------------------------------------
- [NO]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Any relevant logs, error output, etc?
-------------------------------------
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
## Other information
-------------------------------------
<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->M22 - Release 0.25Yunhua KoglinYunhua Koglinhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/496Remove SNAPSHOT dependencies2023-12-08T23:05:48ZDavid 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
```
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: a16ae50eb2640d67eb4aabd8069def2ad7027f98
Maven: 0.25.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------------- | -------------------------- |
| apd-core | 0.24.0-rc1 | |
| core-lib-azure | 0.24.0 | 0.16.0 |
| core-lib-gc | 0.24.0 | |
| core-plus-common-lib | 0.24.0-rc2 | |
| os-core-lib-aws | 0.25.0-SNAPSHOT | 0.25.0-SNAPSHOT |
| obm | 0.24.0 | |
| oqm | 0.24.0 | |
| os-core-common | 0.25.0-rc2 | 0.24.0, 0.16.0, 0.25.0-rc2 |
| os-core-lib-ibm | 0.24.0 | 0.24.0 |
| os-obm-core | 0.25.0-rc1 | |
| os-oqm-core | 0.25.0-rc1 | |
| os-osm-core | 0.25.0-rc1 | |
| osm | 0.24.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.0, 2.13.4.2 | 2.13.2.2, 2.10.3 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.17.2, 2.13.3, 2.11.2 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.17.2, 2.11.2, 2.13.3 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 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: snapshot-removal
SHA: 8a99ba0d961c5599bd56f0fc271582e8b0535840
Maven: 0.25.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | ---------------- | -------------------------- |
| apd-core | 0.24.0-rc1 | |
| core-lib-azure | 0.24.0 | 0.16.0 |
| core-lib-gc | 0.24.0 | |
| core-plus-common-lib | 0.24.0-rc2 | |
| os-core-lib-aws | 0.25.0-rc2 | 0.25.0-rc2 |
| obm | 0.24.0 | |
| oqm | 0.24.0 | |
| os-core-common | 0.25.0-rc2 | 0.24.0, 0.16.0, 0.25.0-rc2 |
| os-core-lib-ibm | 0.24.0 | 0.24.0 |
| os-obm-core | 0.25.0-rc1 | |
| os-oqm-core | 0.25.0-rc1 | |
| os-osm-core | 0.25.0-rc1 | |
| osm | 0.24.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.0, 2.13.4.2 | 2.13.2.2, 2.10.3 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.17.2, 2.13.3, 2.11.2 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.17.2, 2.11.2, 2.13.3 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 1.27, 2.0 |M22 - Release 0.25https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/495Gonrg 8944 - remove legal bootstrap2023-12-08T17:38:09ZAliaksandr Ramanovich (EPAM)Gonrg 8944 - remove legal bootstrapGC only changes:
Move legal bootstrap from service repo to data bootstrapGC only changes:
Move legal bootstrap from service repo to data bootstrapM22 - Release 0.25Aliaksandr Ramanovich (EPAM)Aliaksandr Ramanovich (EPAM)https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/494[MSCOSDU-1857] fix json vulnerability2023-12-12T04:00:12ZVidyaDharani Lokam[MSCOSDU-1857] fix json vulnerability# Change details
* upgraded `core-lib-azure` to `0.25.0-rc2` to remediate `org.json:json` vulnerability
* upgrade `io.netty:netty-bom` version to `4.1.101.Final`
* upgrade `reactor-netty-http` version to `1.1.13`
# Changes in:
* [ ] G...# Change details
* upgraded `core-lib-azure` to `0.25.0-rc2` to remediate `org.json:json` vulnerability
* 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/security-and-compliance/legal/-/merge_requests/493Draft: fix json vulnerability2023-12-07T14:15:12ZVidyaDharani LokamDraft: fix json vulnerabilityVidyaDharani LokamVidyaDharani Lokamhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/492Changed logic with default legal file.2023-12-07T13:44:34ZRiabokon Stanislav(EPAM)[GCP]Changed logic with default legal file.## Type of change
- [ ] Bug Fix
- [X] Feature
## 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
- [x] GC
- [ ] IBM...## Type of change
- [ ] Bug Fix
- [X] Feature
## 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
- [x] GC
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the old behavior?
![image](/uploads/a6d3af630dd912041829f800180f4a10/image.png)
## What is the new/expected behavior?
A default GC was removed in favor of a common default file. Changed int/unit tests. Updated documentation.
Removed a flag 'full_bucket_name'.
![image](/uploads/38f022cc6a61b18995f569e1fbd338a7/image.png)
## Have you added/updated Unit Tests and Integration Tests?
YesM23 - Release 0.26Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/491Draft: Gonrg 8875 disabling legal bootstrap2023-12-08T10:08:12ZSiarhei Poliak [EPAM / GCP]Draft: Gonrg 8875 disabling legal bootstrap## All Submissions:
-------------------------------------
* [NO] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [NO] I have added tests t...## All Submissions:
-------------------------------------
* [NO] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [NO] I have added tests to cover my changes.
* [NA] All new and existing tests passed.
* [YES] My code follows the code style of this project.
* [YES] I ran lint checks locally prior to submission.
## What is the current behavior?
-------------------------------------
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
Issue: Remember to link the workitem to this pull request.
It looks like the default legal tag is not required for all partitions
## What is the new behavior?
-------------------------------------
<!-- Please describe the behavior or changes that are being added by this PR. -->
Move it to data upload scripts
-
-
-
## Does this introduce a breaking change?
-------------------------------------
- [NO]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Any relevant logs, error output, etc?
-------------------------------------
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
## Other information
-------------------------------------
<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->M23 - Release 0.26https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/490update os-core-common in testing projects2023-12-07T00:26:53ZSolomon Ayalewupdate os-core-common in testing projects## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [NA] I have added tests ...## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [NA] I have added tests to cover my changes.
* [YES/NO] All new and existing tests passed.
* [YES] My code follows the code style of this project.
* [NA] I ran lint checks locally prior to submission.
## What is the current behavior?
-------------------------------------
Issue: https://app.asana.com/0/1205234364005853/1205708822570592/f
## What is the new behavior?
-------------------------------------
<!-- Please describe the behavior or changes that are being added by this PR. -->
No change
## Does this introduce a breaking change?
-------------------------------------
- [NO]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Any relevant logs, error output, etc?
-------------------------------------
## Other information
-------------------------------------M22 - Release 0.25https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/489fix aws core lib version2023-12-05T20:49:52ZYunhua Koglinfix aws core lib version## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [NO] I have added tests ...## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [NO] I have added tests to cover my changes.
* [YES] All new and existing tests passed.
* [YES] My code follows the code style of this project.
* [YES] I ran lint checks locally prior to submission.
## What is the current behavior?
-------------------------------------
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
Issue: Remember to link the workitem to this pull request.
## What is the new behavior?
-------------------------------------
<!-- Please describe the behavior or changes that are being added by this PR. -->
-
-
-
## Does this introduce a breaking change?
-------------------------------------
- [YES/NO]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Any relevant logs, error output, etc?
-------------------------------------
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
## Other information
-------------------------------------
<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->M22 - Release 0.25Yunhua KoglinYunhua Koglinhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/488Revert "Merge branch 'search_legal' into 'master'"2024-01-25T11:41:02ZRiabokon Stanislav(EPAM)[GCP]Revert "Merge branch 'search_legal' into 'master'"## All Submissions:
-------------------------------------
* [YES/NO] I have added an explanation of what changes in this merge do and why we should include it?
* [YES/NO] I have updated the documentation accordingly.
* [YES/NO/NA] I have...## All Submissions:
-------------------------------------
* [YES/NO] I have added an explanation of what changes in this merge do and why we should include it?
* [YES/NO] I have updated the documentation accordingly.
* [YES/NO/NA] I have added tests to cover my changes.
* [YES/NO/NA] All new and existing tests passed.
* [YES/NO/NA] My code follows the code style of this project.
* [YES/NO/NA] I ran lint checks locally prior to submission.
## What is the current behavior?
-------------------------------------
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
Issue: Remember to link the workitem to this pull request.
## What is the new behavior?
-------------------------------------
<!-- Please describe the behavior or changes that are being added by this PR. -->
-
-
-
## Does this introduce a breaking change?
-------------------------------------
- [YES/NO]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
## Any relevant logs, error output, etc?
-------------------------------------
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
## Other information
-------------------------------------
<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->M22 - Release 0.25https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/487Query API for legal.2024-02-16T19:46:15ZShane HutchinsQuery API for legal.## All Submissions:
---
* \[YES/NO\] I have added an explanation of what changes in this merge do and why we should include it?
* \[YES\] I have updated the documentation accordingly.
* \[YES\] I have added tests to cover my changes.
*...## All Submissions:
---
* \[YES/NO\] I have added an explanation of what changes in this merge do and why we should include it?
* \[YES\] I have updated the documentation accordingly.
* \[YES\] I have added tests to cover my changes.
* \[YES\] All new and existing tests passed.
* \[YES\] My code follows the code style of this project.
* \[NO\] I ran lint checks locally prior to submission.
## What is the current behavior?
---
## What is the new behavior?
---
- New API in legal tag services to support search. It addresses a subset requirements from https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/36 and https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/47
- Updated documentation
- Updated unit tests
## Does this introduce a breaking change?
---
- \[NO\] - new API but no breaking changes.
## Any relevant logs, error output, etc?
---
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
## Other information
- Documentation update and support of gitlab pages
- Notice update
---M23 - Release 0.26Shane HutchinsShane Hutchinshttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/486Search legal2023-12-28T13:24:14ZShane HutchinsSearch legal## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [YES] I have added tests...## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [YES] I have updated the documentation accordingly.
* [YES] I have added tests to cover my changes. Some test(s) added, additional tests via AdminCLI
* [YES] All new and existing tests passed.
* [YES] My code follows the code style of this project.
* [NO] I ran lint checks locally prior to submission.
## What is the current behavior?
-------------------------------------
## What is the new behavior?
-------------------------------------
<!-- Please describe the behavior or changes that are being added by this PR. -->
- New /query API to address part of the request(s) in
https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/47 and https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/36
## Does this introduce a breaking change?
-------------------------------------
- [NO]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->M22 - Release 0.25Shane HutchinsShane Hutchins