Partition merge requestshttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests2023-08-18T15:32:54Zhttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/73Changed authorize_api to v22023-08-18T15:32:54ZOleksii Tsyganov (EPAM)Changed authorize_api to v2M7 - Release 0.10Oleksii Tsyganov (EPAM)Oleksii Tsyganov (EPAM)https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/66Changed fossa2023-08-18T15:33:01ZOleksii Tsyganov (EPAM)Changed fossaM7 - Release 0.10Oleksii Tsyganov (EPAM)Oleksii Tsyganov (EPAM)https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/400changed kube sa name2023-07-28T13:04:08ZOrest Khud [EPAMĀ / GCP]changed kube sa nameM20 - Release 0.23https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/418Change GC domain Values2023-08-18T15:29:12ZYauheny Boika[EPAM / GCP]Change GC domain ValuesM20 - Release 0.23https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/463Change placement of HttpRequestWithoutValidUrl integration test2023-10-18T14:21:08ZNeha KhandelwalChange placement of HttpRequestWithoutValidUrl integration testCurrently, the should_return400_when_makingHttpRequestWithoutValidUrl integration test is in partition-test-core. However, this test should be moved to partition-test-azure as it corresponds to a Azure specific change.Currently, the should_return400_when_makingHttpRequestWithoutValidUrl integration test is in partition-test-core. However, this test should be moved to partition-test-azure as it corresponds to a Azure specific change.https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/453Change response code for RequestRejectedException2023-10-16T10:51:42ZNeha KhandelwalChange response code for RequestRejectedExceptionAdd RequestRejectedHandler to change the response code to 400 when there is a RequestRejectedException.
Related issue #34.Add RequestRejectedHandler to change the response code to 400 when there is a RequestRejectedException.
Related issue #34.M21 - Release 0.24Chad LeongChad Leonghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/256Change version of azure core lib to 0.17.0-rc7.2022-08-23T16:40:35ZAkshat JoshiChange version of azure core lib to 0.17.0-rc7.https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/255Change version of azure core lib to 0.17.0-rc7.2022-08-20T19:41:15ZAkshat JoshiChange version of azure core lib to 0.17.0-rc7.https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/272Checkov Findings and Gitlab Helm Chart Deploy Variables2022-09-28T19:02:40ZMarc Burnie [AWS]Checkov Findings and Gitlab Helm Chart Deploy VariablesM14 - Release 0.17Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/348Cherry-pick 'adding support for EKS 1.23' into release/0.192023-02-11T01:56:38ZMarc Burnie [AWS]Cherry-pick 'adding support for EKS 1.23' into release/0.19Adding support for EKS 1.23
Original MR: osdu/platform/system/partition!346
(cherry picked from commit 6c78dee5744a2b036006b5f87a6d140661a4e0a6)
7ab27469 Upgrade core-common to 0.19.0-rc6
1f873c4f adding support for EKS 1.23Adding support for EKS 1.23
Original MR: osdu/platform/system/partition!346
(cherry picked from commit 6c78dee5744a2b036006b5f87a6d140661a4e0a6)
7ab27469 Upgrade core-common to 0.19.0-rc6
1f873c4f adding support for EKS 1.23M16 - Release 0.19David Diederichd.diederich@opengroup.orgMarc Burnie [AWS]David Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/405Cherry-pick 'Adding versions to the provider POMs' into release/0.212023-06-07T10:12:27ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Adding versions to the provider POMs' into release/0.21**Original MR**: !404
### 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**: !404
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/system/partition/-/pipelines/new?ref=cherry-pick-for-404)M18 - Release 0.21David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/81cherry-pick 'Configurable partition admin accounts (GONRG-2687)' into release...2021-08-11T13:55:38ZDavid Diederichd.diederich@opengroup.orgcherry-pick 'Configurable partition admin accounts (GONRG-2687)' into release/0.10Original MR: !78Original MR: !78M7 - Release 0.10David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/378Cherry-pick 'Full Upgrade of First Party Library Dependencies for Release 0.2...2023-04-13T08:49:37ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Full Upgrade of First Party Library Dependencies for Release 0.20' into release/0.20**Original MR**: !375
### 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**: !375
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/system/partition/-/pipelines/new?ref=cherry-pick-for-375)M17 - Release 0.20David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/502Cherry-pick 'Full Upgrade of First Party Library Dependencies for Release 0.2...2023-12-16T10:25:20ZDavid 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/system/partition/-/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/system/partition/-/merge_requests/358Cherry-pick 'GONRG-6682: Update partition bootstrap' into release/0.192023-03-06T15:32:57ZVolodymyr Pienskoi [EPAM / GCP]Cherry-pick 'GONRG-6682: Update partition bootstrap' into release/0.19GONRG-6682: Update partition bootstrap
See merge request !357
(cherry picked from commit 5306f0cf)GONRG-6682: Update partition bootstrap
See merge request !357
(cherry picked from commit 5306f0cf)M16 - Release 0.19Volodymyr Pienskoi [EPAM / GCP]Volodymyr Pienskoi [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/434Cherry-pick 'GONRG-7705: add property to partition' into release/0.232023-08-31T21:48:51ZYauheni Rykhter (EPAM)Cherry-pick 'GONRG-7705: add property to partition' into release/0.23**Original MR**: !433
### 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**: !433
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/system/partition/-/pipelines/new?ref=cherry-pick-433)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongYauheni Rykhter (EPAM)David Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/432Cherry-pick 'GONRG-7705: add property to partition' into release/0.232023-09-04T06:15:46ZSrinivasan NarayananCherry-pick 'GONRG-7705: add property to partition' into release/0.23**Original MR**: !430
### 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**: !430
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/system/partition/-/pipelines/new?ref=cherry-pick-for-430)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/424Cherry-picking azure/m16-master into azure/m18-master2023-08-16T17:57:13ZAdrian SaliCherry-picking azure/m16-master into azure/m18-masterAdding support for EKS 1.23
See merge request osdu/platform/system/partition!346
(cherry picked from commit 6c78dee5744a2b036006b5f87a6d140661a4e0a6)
13dae629 Merge remote-tracking branch 'origin/master' into master-dev-merge
a9db3217...Adding support for EKS 1.23
See merge request osdu/platform/system/partition!346
(cherry picked from commit 6c78dee5744a2b036006b5f87a6d140661a4e0a6)
13dae629 Merge remote-tracking branch 'origin/master' into master-dev-merge
a9db3217 Merge remote-tracking branch 'origin/master' into master-dev-merge
3fd07361 Merge remote-tracking branch 'origin/master' into master-dev-merge
7ab27469 Upgrade core-common to 0.19.0-rc6
e901feed Merge remote-tracking branch 'origin/master' into master-dev-merge
1f873c4f adding support for EKS 1.23
bc2602e9 Update NOTICEhttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/505Cherry-pick 'Integration test fixed' into release/0.252023-12-18T16:58:41ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Integration test fixed' into release/0.25**Original MR**: !504
### 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**: !504
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/system/partition/-/pipelines/new?ref=cherry-pick-for-504)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/128Cherry-pick Log4j 2.17 fixes into release/0.122021-12-21T00:12:50ZDavid Diederichd.diederich@opengroup.orgCherry-pick Log4j 2.17 fixes into release/0.12Original MR: !127
Part of the #25 SeriesOriginal MR: !127
Part of the #25 SeriesDavid Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.org