Legal merge requestshttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests2024-03-29T11:04:26Zhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/545Fix Auth filter for Legal Update Status endpoint2024-03-29T11:04:26ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comFix Auth filter for Legal Update Status endpoint## What is the current behavior?
-------------------------------------
/jobs/updateLegalTagStatus is not accessible. Filter configuration does not allow requests.
## What is the new behavior?
-------------------------------------
/jobs...## What is the current behavior?
-------------------------------------
/jobs/updateLegalTagStatus is not accessible. Filter configuration does not allow requests.
## What is the new behavior?
-------------------------------------
/jobs/updateLegalTagStatus is accessible, auth check goes as usual through the Entitlements service.
## Does this introduce a breaking change?
-------------------------------------
- [NO]M23 - Release 0.26Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/543[GONRG-9422]: Remove springProfilesActive explicit setting2024-03-20T12:34:05ZMykola Ronik [EPAM / GCP][GONRG-9422]: Remove springProfilesActive explicit setting## 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.
* [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?
-------------------------------------
https://jiraeu.epam.com/browse/GONRG-9422
## Does this introduce a breaking change?
-------------------------------------
- [NO]M23 - Release 0.26Mykola Ronik [EPAM / GCP]Mykola Ronik [EPAM / GCP]https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/538[GONRG-9211] Added labels to gc helm2024-03-19T17:08:58ZDanylo Vanin (EPAM)[GONRG-9211] Added labels to gc helmM23 - Release 0.26Danylo Vanin (EPAM)Danylo Vanin (EPAM)https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/537Fix cloud sdk image2024-03-05T13:27:42ZSiarhei Poliak [EPAM / GCP]Fix cloud sdk image## All Submissions:
-------------------------------------
* [NO] I have added an explanation of what changes in this merge do and why we should include it?
* [NO] I have updated the documentation accordingly.
* [NO] I have added tests to...## All Submissions:
-------------------------------------
* [NO] I have added an explanation of what changes in this merge do and why we should include it?
* [NO] 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?
-------------------------------------
- [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/535Extend cron to catch about to expire legal tags2024-03-19T14:08:18ZKonrad KrasnodebskiExtend cron to catch about to expire legal tagsChanges related to [ADR](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/52)
- Existing cron job for checking expired legal tags is extended to check about to expire legal tags regarding declared per...Changes related to [ADR](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/52)
- Existing cron job for checking expired legal tags is extended to check about to expire legal tags regarding declared period to expire.
- Existing legal SNS topic with new item is used.
- **Changes are hidden behind the feature flag**
New SNS topic item:
```
{
"aboutToExpireLegalTags": [
{
"dataPartitionId":"osdu",
"tagName":"osdu-public-usa-dataset-osduonaws-test-about-to-expire",
"expirationDate":"Mar 15, 2024"
}
]
}
```
Info in logs about catching about to expire legal tag:
![image](/uploads/4284542ae997fdb0fcf2ba09a6bcf552/image.png)M23 - Release 0.26https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/534[#MSCOSDU-35627] upgrade : core-lib-azure Java 17 version2024-02-29T06:55:12ZThulasi Dass Subramanian[#MSCOSDU-35627] upgrade : core-lib-azure Java 17 version## Change details
* For Azure only: upgraded `core-lib-azure` version to `0.26.0-rc5` for Java 17 updates
## Changes in:
* [ ] GCP
* [x] Azure
* [ ] AWS
* [ ] IBM## Change details
* For Azure only: upgraded `core-lib-azure` version to `0.26.0-rc5` for Java 17 updates
## Changes in:
* [ ] GCP
* [x] Azure
* [ ] AWS
* [ ] IBMM23 - Release 0.26Thulasi Dass SubramanianThulasi Dass Subramanianhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/533Aws fix 500 errors2024-02-27T14:19:12ZDerek HudsonAws fix 500 errors## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [NA] 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?
* [NA] 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.
* [YES] I ran lint checks locally prior to submission.
## What is the current behavior?
-------------------------------------
500 errors in AWS when the behavior should be to respond with 401 or 400 errors.
## What is the new behavior?
-------------------------------------
<!-- Please describe the behavior or changes that are being added by this PR. -->
Now responds with 401 errors when certain things happen (mostly invalid data partition IDs).
## 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.26Derek HudsonDerek Hudsonhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/529Refactor Swagger Configuration to use '@ConfigurationProperties' from '@Value'2024-02-15T12:47:52ZAnthony Ittiyera vazhappillyRefactor Swagger Configuration to use '@ConfigurationProperties' from '@Value'
* This PR enables the swaggerConfiguration to use ConfigurationProperty to bind properties to the properties present in the properties files.
* This is not a breaking change; this makes it consistent across other services as well.
* This PR enables the swaggerConfiguration to use ConfigurationProperty to bind properties to the properties present in the properties files.
* This is not a breaking change; this makes it consistent across other services as well.M23 - Release 0.26https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/528Update lib2024-03-19T17:08:59ZRucha DeshpandeUpdate lib## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [NA] I have updated the documentation accordingly.
* [NA I have added tests to...## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [NA] 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. -->
- Update AWS os-core-lib-aws
-
-
## 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/525GONRG-9182: add cronjob2024-02-05T09:38:55ZYauheni Rykhter (EPAM)GONRG-9182: add cronjobM23 - Release 0.26Yauheni Rykhter (EPAM)Yauheni Rykhter (EPAM)https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/524Comm Imp update property, to fix bucket name2024-02-02T09:16:26ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comComm Imp update property, to fix bucket name## 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. -->M23 - Release 0.26Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/523Jakarta EE, Spring 6, Spring-Boot 3 migration2024-03-12T14:59:13ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comJakarta EE, Spring 6, Spring-Boot 3 migrationRelated issue: https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/69
# Description:
- Migration to Spring 6+, Spring-Boot 3+, and replacement of Javax by Jakarta EE.
- Changed javax. imports to jakart...Related issue: https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/69
# Description:
- Migration to Spring 6+, Spring-Boot 3+, and replacement of Javax by Jakarta EE.
- Changed javax. imports to jakarta.
- Spring Security configuration migration, https://spring.io/blog/2022/02/21/spring-security-without-the-websecurityconfigureradapter
- Migration to springdoc-openapi 2.0+ https://springdoc.org/#what-is-the-compatibility-matrix-of-springdoc-openapi-with-spring-boot
- Used Core-Common fork compatible with mentioned dependencies. https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common-spring6
- Not supported BYOC module is dropped.
# How to test:
Integration tests.
# Changes include:
- [ ] Refactor (a non-breaking change that improves code maintainability).
- [ ] Bugfix (a non-breaking change that solves an issue).
- [ ] New feature (a non-breaking change that adds functionality).
- [x] Breaking change (a change that is not backward-compatible and/or changes current functionality).
# Changes in:
- [x] GC
- [x] Azure
- [x] AWS
- [x] IBM
- [x] Common Code
- [x] Community Impl
# Other comments:
`mvn dependency:tree -Dincludes="org.springframework.*"`
<details><summary>Click to expand</summary>
~~~
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] legal-service [pom]
[INFO] legal-core [jar]
[INFO] legal-core-plus [jar]
[INFO] legal-gc [jar]
[INFO] legal-azure [jar]
[INFO] legal-aws [jar]
[INFO] legal-ibm [jar]
[INFO]
[INFO] ---------------< org.opengroup.osdu.legal:legal-service >---------------
[INFO] Building legal-service 0.26.0-SNAPSHOT [1/7]
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ legal-service ---
[INFO] org.opengroup.osdu.legal:legal-service:pom:0.26.0-SNAPSHOT
[INFO] \- org.springdoc:springdoc-openapi-starter-webmvc-ui:jar:2.3.0:compile
[INFO] \- org.springdoc:springdoc-openapi-starter-webmvc-api:jar:2.3.0:compile
[INFO] \- org.springdoc:springdoc-openapi-starter-common:jar:2.3.0:compile
[INFO] \- org.springframework.boot:spring-boot-autoconfigure:jar:3.2.3:compile
[INFO] \- org.springframework.boot:spring-boot:jar:3.2.3:compile
[INFO]
[INFO] ----------------< org.opengroup.osdu.legal:legal-core >-----------------
[INFO] Building legal-core 0.26.0-SNAPSHOT [2/7]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ legal-core ---
[INFO] org.opengroup.osdu.legal:legal-core:jar:0.26.0-SNAPSHOT
[INFO] +- org.springframework.boot:spring-boot-starter-actuator:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-starter:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot-autoconfigure:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-starter-logging:jar:3.2.3:compile
[INFO] | \- org.springframework.boot:spring-boot-actuator-autoconfigure:jar:3.2.3:compile
[INFO] | \- org.springframework.boot:spring-boot-actuator:jar:3.2.3:compile
[INFO] +- org.springframework.boot:spring-boot-starter-web:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-json:jar:3.2.3:compile
[INFO] | \- org.springframework.boot:spring-boot-starter-tomcat:jar:3.2.3:compile
[INFO] +- org.springframework.boot:spring-boot-starter-security:jar:3.2.3:compile
[INFO] | +- org.springframework.security:spring-security-config:jar:6.2.2:compile
[INFO] | \- org.springframework.security:spring-security-web:jar:6.2.2:compile
[INFO] +- org.springframework.boot:spring-boot-starter-validation:jar:3.2.3:compile
[INFO] +- org.springframework.boot:spring-boot-starter-test:jar:3.2.3:test
[INFO] | +- org.springframework.boot:spring-boot-test:jar:3.2.3:test
[INFO] | \- org.springframework.boot:spring-boot-test-autoconfigure:jar:3.2.3:test
[INFO] \- org.springframework.security:spring-security-test:jar:6.2.2:test
[INFO] \- org.springframework.security:spring-security-core:jar:6.2.2:compile
[INFO] \- org.springframework.security:spring-security-crypto:jar:6.2.2:compile
[INFO]
[INFO] --------------< org.opengroup.osdu.legal:legal-core-plus >--------------
[INFO] Building legal-core-plus 0.26.0-SNAPSHOT [3/7]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ legal-core-plus ---
[INFO] org.opengroup.osdu.legal:legal-core-plus:jar:0.26.0-SNAPSHOT
[INFO] +- org.springframework.boot:spring-boot-loader:jar:3.2.3:compile
[INFO] +- org.opengroup.osdu.legal:legal-core:jar:0.26.0-SNAPSHOT:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-actuator:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-actuator-autoconfigure:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-actuator:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-web:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot-starter-json:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-starter-tomcat:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-security:jar:3.2.3:compile
[INFO] | \- org.springframework.boot:spring-boot-starter-validation:jar:3.2.3:compile
[INFO] +- org.springframework.boot:spring-boot-starter-test:jar:3.2.3:test
[INFO] | +- org.springframework.boot:spring-boot-starter:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot-autoconfigure:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-starter-logging:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-test:jar:3.2.3:test
[INFO] | \- org.springframework.boot:spring-boot-test-autoconfigure:jar:3.2.3:test
[INFO] +- org.springframework.security:spring-security-test:jar:6.2.2:test
[INFO] | +- org.springframework.security:spring-security-core:jar:6.2.2:compile
[INFO] | | \- org.springframework.security:spring-security-crypto:jar:6.2.2:compile
[INFO] | \- org.springframework.security:spring-security-web:jar:6.2.2:compile
[INFO] \- org.springframework.security:spring-security-config:jar:6.2.2:compile
[INFO]
[INFO] -----------------< org.opengroup.osdu.legal:legal-gc >------------------
[INFO] Building legal-gc 0.26.0-SNAPSHOT [4/7]
[INFO] --------------------------------[ jar ]---------------------------------
[WARNING] Could not transfer metadata com.nimbusds:lang-tag/maven-metadata.xml from/to ${repo.releases.id} (${repo.releases.url}): Cannot access ${repo.releases.url} with type default using the available connector factories: BasicRepositoryConnectorFactory
[WARNING] Could not transfer metadata com.nimbusds:nimbus-jose-jwt/maven-metadata.xml from/to ${repo.releases.id} (${repo.releases.url}): Cannot access ${repo.releases.url} with type default using the available connector factories: BasicRepositoryConnectorFactory
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ legal-gc ---
[WARNING] com.nimbusds:lang-tag/maven-metadata.xmlfailed to transfer from ${repo.releases.url} during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of ${repo.releases.id} has elapsed or updates are forced. Original error: Could not transfer metadata com.nimbusds:lang-tag/maven-metadata.xml from/to ${repo.releases.id} (${repo.releases.url}): Cannot access ${repo.releases.url} with type default using the available connector factories: BasicRepositoryConnectorFactory
[WARNING] com.nimbusds:nimbus-jose-jwt/maven-metadata.xmlfailed to transfer from ${repo.releases.url} during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of ${repo.releases.id} has elapsed or updates are forced. Original error: Could not transfer metadata com.nimbusds:nimbus-jose-jwt/maven-metadata.xml from/to ${repo.releases.id} (${repo.releases.url}): Cannot access ${repo.releases.url} with type default using the available connector factories: BasicRepositoryConnectorFactory
[INFO] org.opengroup.osdu.legal:legal-gc:jar:0.26.0-SNAPSHOT
[INFO] +- org.opengroup.osdu.legal:legal-core:jar:0.26.0-SNAPSHOT:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-actuator:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-actuator-autoconfigure:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-actuator:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-web:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot-starter-json:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-starter-tomcat:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-security:jar:3.2.3:compile
[INFO] | | \- org.springframework.security:spring-security-config:jar:6.2.2:compile
[INFO] | \- org.springframework.boot:spring-boot-starter-validation:jar:3.2.3:compile
[INFO] +- org.springframework.boot:spring-boot-starter-test:jar:3.2.3:test
[INFO] | +- org.springframework.boot:spring-boot-starter:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot-autoconfigure:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-starter-logging:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-test:jar:3.2.3:test
[INFO] | \- org.springframework.boot:spring-boot-test-autoconfigure:jar:3.2.3:test
[INFO] +- org.springframework.security:spring-security-test:jar:6.2.2:test
[INFO] | +- org.springframework.security:spring-security-core:jar:6.2.2:compile
[INFO] | | \- org.springframework.security:spring-security-crypto:jar:6.2.2:compile
[INFO] | \- org.springframework.security:spring-security-web:jar:6.2.2:compile
[INFO] \- org.opengroup.osdu:osm:jar:0.25.0:compile
[INFO] \- org.springframework.boot:spring-boot-starter-jdbc:jar:3.2.3:compile
[INFO]
[INFO] ----------------< org.opengroup.osdu.legal:legal-azure >----------------
[INFO] Building legal-azure 0.26.0-SNAPSHOT [5/7]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ legal-azure ---
[INFO] org.opengroup.osdu.legal:legal-azure:jar:0.26.0-SNAPSHOT
[INFO] +- org.opengroup.osdu.legal:legal-core:jar:0.26.0-SNAPSHOT:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-actuator:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-actuator-autoconfigure:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-actuator:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-web:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot-starter-json:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-starter-tomcat:jar:3.2.3:compile
[INFO] | \- org.springframework.boot:spring-boot-starter-validation:jar:3.2.3:compile
[INFO] +- com.azure.spring:spring-cloud-azure-starter-active-directory:jar:5.10.0:compile
[INFO] | +- org.springframework.security:spring-security-web:jar:6.2.2:compile
[INFO] | \- org.springframework.security:spring-security-config:jar:6.2.2:compile
[INFO] +- org.springframework.boot:spring-boot-starter-security:jar:3.2.3:compile
[INFO] | \- org.springframework.boot:spring-boot-starter:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-autoconfigure:jar:3.2.3:compile
[INFO] | \- org.springframework.boot:spring-boot-starter-logging:jar:3.2.3:compile
[INFO] +- org.springframework.security:spring-security-oauth2-client:jar:6.2.2:compile
[INFO] | +- org.springframework.security:spring-security-core:jar:6.2.2:compile
[INFO] | | \- org.springframework.security:spring-security-crypto:jar:6.2.2:compile
[INFO] | \- org.springframework.security:spring-security-oauth2-core:jar:6.2.2:compile
[INFO] +- org.springframework.security:spring-security-oauth2-jose:jar:6.2.2:compile
[INFO] +- org.opengroup.osdu:core-lib-azure-spring6:jar:0.26.0-rc6:compile
[INFO] | +- com.azure:azure-spring-data-cosmos:jar:5.9.1:compile
[INFO] | | \- org.springframework.data:spring-data-commons:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-log4j2:jar:3.2.3:compile
[INFO] | \- org.springframework.boot:spring-boot-starter-aop:jar:3.2.3:compile
[INFO] \- org.springframework.boot:spring-boot-starter-test:jar:3.2.3:test
[INFO] +- org.springframework.boot:spring-boot-test:jar:3.2.3:test
[INFO] \- org.springframework.boot:spring-boot-test-autoconfigure:jar:3.2.3:test
[INFO]
[INFO] -----------------< org.opengroup.osdu.legal:legal-aws >-----------------
[INFO] Building legal-aws 0.26.0-SNAPSHOT [6/7]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ legal-aws ---
[INFO] org.opengroup.osdu.legal:legal-aws:jar:0.26.0-SNAPSHOT
[INFO] +- org.opengroup.osdu.core.aws:os-core-lib-aws:jar:0.26.0-spring6-rc1:compile
[INFO] | +- org.springframework.boot:spring-boot-dependencies:pom:3.2.2:compile
[INFO] | \- org.springframework.data:spring-data-mongodb:jar:4.2.3:compile
[INFO] | \- org.springframework.data:spring-data-commons:jar:3.2.3:compile
[INFO] +- org.opengroup.osdu.legal:legal-core:jar:0.26.0-SNAPSHOT:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-actuator:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-actuator-autoconfigure:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-actuator:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-web:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot-starter-json:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-starter-tomcat:jar:3.2.3:compile
[INFO] | \- org.springframework.boot:spring-boot-starter-validation:jar:3.2.3:compile
[INFO] +- org.springframework.boot:spring-boot-starter-security:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-starter:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot-autoconfigure:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-starter-logging:jar:3.2.3:compile
[INFO] | +- org.springframework.security:spring-security-config:jar:6.2.2:compile
[INFO] | \- org.springframework.security:spring-security-web:jar:6.2.2:compile
[INFO] +- org.springframework.security:spring-security-oauth2-client:jar:6.2.2:compile
[INFO] | +- org.springframework.security:spring-security-core:jar:6.2.2:compile
[INFO] | | \- org.springframework.security:spring-security-crypto:jar:6.2.2:compile
[INFO] | \- org.springframework.security:spring-security-oauth2-core:jar:6.2.2:compile
[INFO] +- org.springframework.security:spring-security-oauth2-jose:jar:6.2.2:compile
[INFO] +- org.springframework.boot:spring-boot-starter-test:jar:3.2.3:test
[INFO] | +- org.springframework.boot:spring-boot-test:jar:3.2.3:test
[INFO] | \- org.springframework.boot:spring-boot-test-autoconfigure:jar:3.2.3:test
[INFO] \- org.springframework.security:spring-security-test:jar:6.2.2:test
[INFO]
[INFO] -----------------< org.opengroup.osdu.legal:legal-ibm >-----------------
[INFO] Building legal-ibm 0.26.0-SNAPSHOT [7/7]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ legal-ibm ---
[INFO] org.opengroup.osdu.legal:legal-ibm:jar:0.26.0-SNAPSHOT
[INFO] +- org.opengroup.osdu.legal:legal-core:jar:0.26.0-SNAPSHOT:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-actuator:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-actuator-autoconfigure:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-actuator:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-web:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot-starter-json:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-starter-tomcat:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-starter-security:jar:3.2.3:compile
[INFO] | | \- org.springframework.security:spring-security-config:jar:6.2.2:compile
[INFO] | \- org.springframework.boot:spring-boot-starter-validation:jar:3.2.3:compile
[INFO] +- org.springframework.boot:spring-boot:jar:3.2.3:compile
[INFO] +- org.springframework.boot:spring-boot-starter-test:jar:3.2.3:test
[INFO] | +- org.springframework.boot:spring-boot-starter:jar:3.2.3:compile
[INFO] | | +- org.springframework.boot:spring-boot-autoconfigure:jar:3.2.3:compile
[INFO] | | \- org.springframework.boot:spring-boot-starter-logging:jar:3.2.3:compile
[INFO] | +- org.springframework.boot:spring-boot-test:jar:3.2.3:test
[INFO] | \- org.springframework.boot:spring-boot-test-autoconfigure:jar:3.2.3:test
[INFO] \- org.springframework.security:spring-security-test:jar:6.2.2:test
[INFO] +- org.springframework.security:spring-security-core:jar:6.2.2:compile
[INFO] | \- org.springframework.security:spring-security-crypto:jar:6.2.2:compile
[INFO] \- org.springframework.security:spring-security-web:jar:6.2.2:compile
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for legal-service 0.26.0-SNAPSHOT:
[INFO]
[INFO] legal-service ...................................... SUCCESS [ 0.957 s]
[INFO] legal-core ......................................... SUCCESS [ 0.680 s]
[INFO] legal-core-plus .................................... SUCCESS [ 0.425 s]
[INFO] legal-gc ........................................... SUCCESS [ 1.087 s]
[INFO] legal-azure ........................................ SUCCESS [ 0.531 s]
[INFO] legal-aws .......................................... SUCCESS [ 0.305 s]
[INFO] legal-ibm .......................................... SUCCESS [ 0.287 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.219 s
[INFO] Finished at: 2024-03-12T15:49:55+02:00
[INFO] ------------------------------------------------------------------------
~~~
</details>M23 - Release 0.26Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/521Cherry-pick 'fix analyze yml' into release/0.252024-01-30T13:51:08ZChad LeongCherry-pick 'fix analyze yml' into release/0.25**Original MR**: !519
### 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**: !519
### 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-519)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/520Cherry-pick 'Test compliance fix' into release/0.252024-01-30T09:57:12ZChad LeongCherry-pick 'Test compliance fix' into release/0.25**Original MR**: !518
### 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**: !518
### 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-518)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/519fix analyze yml2024-01-30T13:54:16ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comfix analyze yml## 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. -->M23 - Release 0.26Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/518Test compliance fix2024-01-30T09:48:24ZRucha DeshpandeTest compliance fix## All Submissions:
-------------------------------------
* [YES] I have added an explanation of what changes in this merge do and why we should include it?
* [N/A] 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?
* [N/A] 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.
* [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. -->
The bug and related investigation is explained in the issue linked.
Issue: https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/70
## What is the new behavior?
-------------------------------------
<!-- Please describe the behavior or changes that are being added by this PR. -->
- The compliance API now uses the data-partition-id from within the for loop instead of using the one coming in from the compliance-trigger request
## Does this introduce a breaking change?
-------------------------------------
- [No]
<!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. -->
-------------------------------------
(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.25Rucha DeshpandeRucha Deshpandehttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/516GONRG-8949: added sa for legal cronjob2024-01-26T12:34:53ZMikhail Piatliou (EPAM)GONRG-8949: added sa for legal cronjobM23 - Release 0.26Mikhail Piatliou (EPAM)Mikhail Piatliou (EPAM)https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/515Gonrg 9103 decline the data partition id variable as a system partition2024-01-22T18:51:30ZSiarhei Poliak [EPAM / GCP]Gonrg 9103 decline the data partition id variable as a system partition## 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.
* [NA] 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.
* [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: Wrong README
## What is the new behavior?
-------------------------------------
<!-- Please describe the behavior or changes that are being added by this PR. -->
Right README
-
-
-
## 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/514[MSCOSDU-2024] feat: Configuration for Enable full server url in OpenAPI swag...2024-01-13T00:21:57ZThulasi Dass Subramanian[MSCOSDU-2024] feat: Configuration for Enable full server url in OpenAPI swaggerAPI swagger## Change Details
- 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...## Change Details
- 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/513Cherry-pick 'version updated for ibm fix' into release/0.252024-01-09T16:09:31ZChad LeongCherry-pick 'version updated for ibm fix' into release/0.25**Original MR**: !512
### 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**: !512
### 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-512)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.org