Legal merge requestshttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests2022-02-23T01:12:09Zhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/216Add AWS GroupCache and AuthorizationServiceImpl2022-02-23T01:12:09ZYifei XuAdd AWS GroupCache and AuthorizationServiceImplAdd AWS GroupCache and AuthorizationServiceImpl. Change image.Add AWS GroupCache and AuthorizationServiceImpl. Change image.M11 - Release 0.14Yifei XuOkoun-Ola Fabien HouetoYifei Xuhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/296Add git secrets2022-09-21T15:00:02ZMorris EstepaAdd git secretsAdd git secretsAdd git secretsM14 - Release 0.17Morris EstepaMorris Estepahttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/285Adding AWS Helm Charts2022-08-23T19:20:37ZMarc Burnie [AWS]Adding AWS Helm ChartsM14 - Release 0.17Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/362Adding support for EKS 1.232023-02-10T21:25:07ZMarc Burnie [AWS]Adding support for EKS 1.23M16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/221Add mongodb aws support2022-03-25T12:52:51ZAleh Shubko [EPAM]Add mongodb aws supportM11 - Release 0.14Matt WiseAleh Shubko [EPAM]Okoun-Ola Fabien HouetoMatt Wisehttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/374Add mongodb terraform parameter2023-03-16T13:40:12ZAleh Shubko [EPAM]Add mongodb terraform parameterAWS DevOps Changes OnlyAWS DevOps Changes OnlyM17 - Release 0.20Aleh Shubko [EPAM]Marc Burnie [AWS]Aleh Shubko [EPAM]https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/81allow usage of os-core-lib-aws from GL2023-08-18T11:45:00ZRucha Deshpandeallow usage of os-core-lib-aws from GLM1 - Release 0.1Rucha DeshpandeRucha Deshpandehttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/43AWS Entitlements on ECS2023-08-18T11:47:11ZMatt WiseAWS Entitlements on ECSM1 - Release 0.1https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/483AWS - Merge from dev2023-11-24T14:23:08ZGuillaume CailletAWS - Merge from devAWS changes only. No changes on core logic or other CSP.
* Add or update License header
* Upgrade buildspec
* Add unit tests to AWS codeAWS changes only. No changes on core logic or other CSP.
* Add or update License header
* Upgrade buildspec
* Add unit tests to AWS codeM22 - Release 0.25Guillaume CailletGuillaume Caillethttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/208AWS README and SSL change2022-01-21T22:27:09ZYifei XuAWS README and SSL changeAWS README and SSL changeAWS README and SSL changeM10 - Release 0.13JoeGregYifei XuJoehttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/437AWS sync dev to master2023-08-19T02:36:06ZLong ChengAWS sync dev to masterM20 - Release 0.23Long ChengLong Chenghttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/423AWS sync dev to master2023-07-07T19:35:41ZLong ChengAWS sync dev to 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. -->M19 - Release 0.22Long ChengLong Chenghttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/132AWS Updates2023-08-18T11:41:12ZSpencer Suttonsuttonsp@amazon.comAWS Updatescommit 2e99fe61
Author: Spencer Sutton <suttonsp@amazon.com>
Date: Wed May 26 2021 17:17:03 GMT-0500 (Central Daylight Time)
Dynamic account id in mirror
commit 6284c2cc
Author: Spencer Sutton <suttonsp@amazon.com>
Date: Wed ...commit 2e99fe61
Author: Spencer Sutton <suttonsp@amazon.com>
Date: Wed May 26 2021 17:17:03 GMT-0500 (Central Daylight Time)
Dynamic account id in mirror
commit 6284c2cc
Author: Spencer Sutton <suttonsp@amazon.com>
Date: Wed May 26 2021 17:13:00 GMT-0500 (Central Daylight Time)
Excluding security auto config, restricting central mavenM7 - Release 0.10Spencer Suttonsuttonsp@amazon.comSpencer Suttonsuttonsp@amazon.comhttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/307AWS Using Helm to Deploy2022-10-01T00:04:32ZMarc Burnie [AWS]AWS Using Helm to DeployM14 - Release 0.17Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/363Cherry-pick 'adding support for EKS 1.23' into release/0.192023-02-11T01:58:11ZMarc Burnie [AWS]Cherry-pick 'adding support for EKS 1.23' into release/0.19Original MR: https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/362
Only AWS Helm Chart changesOriginal MR: https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/362
Only AWS Helm Chart changesM16 - Release 0.19David Diederichd.diederich@opengroup.orgMarc Burnie [AWS]David Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/335Cherry-pick 'AWS Integration Merge' into release/0.182022-12-06T13:55:58ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'AWS Integration Merge' into release/0.18**Original MR**: !332
### 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**: !332
### 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-332)M15 - Release 0.18David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://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/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/190Cherry-pick Log4j 2.17 fixes into release/0.122021-12-20T23:37:11ZDavid Diederichd.diederich@opengroup.orgCherry-pick Log4j 2.17 fixes into release/0.12Original MR: !189
Part of the #20 SeriesOriginal MR: !189
Part of the #20 SeriesDavid Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/185Cherry-pick log4j updates into release/0.122021-12-15T16:46:23ZDavid Diederichd.diederich@opengroup.orgCherry-pick log4j updates into release/0.12Original MRs: !176, !183, and !184
(cherry picked from commit 9af46e347007d27b1093602991442b40cd1c5e73)
Part of the #19 seriesOriginal MRs: !176, !183, and !184
(cherry picked from commit 9af46e347007d27b1093602991442b40cd1c5e73)
Part of the #19 seriesDavid Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.org