Partition merge requestshttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests2023-12-18T16:58:41Zhttps://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/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/499Cherry-pick '[MSCOSDU-1865] fix: Upgrade json,netty-http, reactor-netty-http'...2023-12-12T19:24:15ZDavid Diederichd.diederich@opengroup.orgCherry-pick '[MSCOSDU-1865] fix: Upgrade json,netty-http, reactor-netty-http' into release/0.25**Original MR**: !498
### 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**: !498
### 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-498)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/497Merge branch 'gc-fix-pipeline' into 'master'2023-12-11T17:39:51ZMikhail Piatliou (EPAM)Merge branch 'gc-fix-pipeline' into 'master'GONRG-8946: fix rules for pipeline
See merge request osdu/platform/system/partition!496
(cherry picked from commit 2503401658fed0a2f9ca1cfaa4f72b73f8512945)
f11e1488 GONRG-8946: fix rules for pipeline
a5a83991 GONRG-8946: fix rules fo...GONRG-8946: fix rules for pipeline
See merge request osdu/platform/system/partition!496
(cherry picked from commit 2503401658fed0a2f9ca1cfaa4f72b73f8512945)
f11e1488 GONRG-8946: fix rules for pipeline
a5a83991 GONRG-8946: fix rules for pipelineM22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/475Cherry-pick: Merge branch 'gc-fix-bm-bootstrap' into 'release/0.24'2023-10-23T07:34:29ZMikhail Piatliou (EPAM)Cherry-pick: Merge branch 'gc-fix-bm-bootstrap' into 'release/0.24'GONRG-7991: extend bootstrap data
See merge request osdu/platform/system/partition!474
(cherry picked from commit d72a6ef3b9b0cefbf53cdb71baee9b65a36431a6)
8e2dfee4 GONRG-7991: extend bootstrap dataGONRG-7991: extend bootstrap data
See merge request osdu/platform/system/partition!474
(cherry picked from commit d72a6ef3b9b0cefbf53cdb71baee9b65a36431a6)
8e2dfee4 GONRG-7991: extend bootstrap dataM21 - Release 0.24David Diederichd.diederich@opengroup.orgChad LeongDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/471Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.24' into ...2023-10-19T06:31:20ZSrinivasan NarayananCherry-pick 'Upgrade First Party Library Dependencies for Release 0.24' into release/0.24**Original MR**: !464
### 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**: !464
### 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-464)M21 - Release 0.24David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/469Cherry-pick: Merge branch 'request-reject-handler' into 'release/0.24'2023-10-18T08:59:42ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comCherry-pick: Merge branch 'request-reject-handler' into 'release/0.24'make request reject handler global
See merge request osdu/platform/system/partition!468
(cherry picked from commit c59a1bfd7244f0ecf6142c079db97743930f18d9)
7893e4b4 make request reject handler global
b3299ef4 move bean config to conf...make request reject handler global
See merge request osdu/platform/system/partition!468
(cherry picked from commit c59a1bfd7244f0ecf6142c079db97743930f18d9)
7893e4b4 make request reject handler global
b3299ef4 move bean config to config classM21 - Release 0.24https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/446Cherry-pick 'Upgrade Core Azure Library Dependency for Release 0.23' into rel...2023-09-05T21:07:14ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Upgrade Core Azure Library Dependency for Release 0.23' into release/0.23**Original MR**: !444
### 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**: !444
### 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-444)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/438Cherry-pick: Merge MR 435 in release branch2023-09-04T20:37:19ZYauheni Rykhter (EPAM)Cherry-pick: Merge MR 435 in release branchGoogle Cloud specific changes
Refactor Partition bootstrap
See merge request !435 (merged)Google Cloud specific changes
Refactor Partition bootstrap
See merge request !435 (merged)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongYauheni Rykhter (EPAM)Srinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/440Cherry-pick 'Revert "Merge branch 'gc-add-property' into 'master'"' into rele...2023-09-04T20:37:17ZChad LeongCherry-pick 'Revert "Merge branch 'gc-add-property' into 'master'"' into release/0.23**Original MR**: !436
### 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**: !436
### 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-436)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/439Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.23' into ...2023-09-04T18:16:39ZChad LeongCherry-pick 'Upgrade First Party Library Dependencies for Release 0.23' into release/0.23**Original MR**: !429
### 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**: !429
### 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-429)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid 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/428Merge MR 422 in release branch2023-08-31T12:16:54ZAliaksandr Ramanovich (EPAM)Merge MR 422 in release branchGoogle Cloud specific changes
Refactor Elastic bootstrap to work with common credentials
See merge request osdu/platform/system/partition!422
(cherry picked from commit f5cfb6cc39b8a365517506b59be889f32fe5ca05)
59082b63 Update data p...Google Cloud specific changes
Refactor Elastic bootstrap to work with common credentials
See merge request osdu/platform/system/partition!422
(cherry picked from commit f5cfb6cc39b8a365517506b59be889f32fe5ca05)
59082b63 Update data partition b2088141 Updating NOTICEM20 - Release 0.23David Diederichd.diederich@opengroup.orgAliaksandr Ramanovich (EPAM)Chad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/420Merge branch 'GONRG-7241-Rename-SA-on-GC-envs' into 'release/0.22'2023-07-31T20:52:12ZAliaksandr Ramanovich (EPAM)Merge branch 'GONRG-7241-Rename-SA-on-GC-envs' into 'release/0.22'Only GC specificchanges
changed kube sa name
See merge request osdu/platform/system/partition!400
(cherry picked from commit 406eabc9122e999d55178eb3d08e38fe476bba96)
18e4fc44 changed kube sa nameOnly GC specificchanges
changed kube sa name
See merge request osdu/platform/system/partition!400
(cherry picked from commit 406eabc9122e999d55178eb3d08e38fe476bba96)
18e4fc44 changed kube sa nameM19 - Release 0.22Aliaksandr Ramanovich (EPAM)Aliaksandr Ramanovich (EPAM)https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/414Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.22' into ...2023-07-14T07:18:04ZChad LeongCherry-pick 'Upgrade First Party Library Dependencies for Release 0.22' into release/0.22**Original MR**: !413
### 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**: !413
### 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-413)M19 - Release 0.22David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid 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/399Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.21' into ...2023-05-31T20:27:20ZChad LeongCherry-pick 'Upgrade First Party Library Dependencies for Release 0.21' into release/0.21**Original MR**: !397
### 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**: !397
### 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-397)M18 - Release 0.21David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid 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/372Merge branch 'GONRG-6771_Update_bootstrap_for_minio_external_endpoint' into '...2023-04-06T11:58:05ZVolodymyr Pienskoi [EPAM / GCP]Merge branch 'GONRG-6771_Update_bootstrap_for_minio_external_endpoint' into 'master'GONRG-6771: Update bootstrap for minio external endpoint
See merge request osdu/platform/system/partition!367
(cherry picked from commit ee05894934b5c54b523bad7fdad50b245ae3811e)
74a020b5 GONRG-6771: Replace file.minio.endpoint with o...GONRG-6771: Update bootstrap for minio external endpoint
See merge request osdu/platform/system/partition!367
(cherry picked from commit ee05894934b5c54b523bad7fdad50b245ae3811e)
74a020b5 GONRG-6771: Replace file.minio.endpoint with obm.minio.external.endpoint
8d02a2e8 GONRG-6771: Add obm.minio.ignoreCertCheck
41449b0e GONRG-6771: Remove file.minio properties
b2720879 GONRG-6771: Update NOTICE
cfc14e22 GONRG-6771: Fix typo
7f24eb44 GONRG-6771: Fix typo
a93a8ed4 Merge branch 'master' into GONRG-6771_Update_bootstrap_for_minio_external_endpointM17 - Release 0.20Volodymyr Pienskoi [EPAM / GCP]Volodymyr Pienskoi [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/partition/-/merge_requests/369Merge branch 'fix-partition-dev2' into 'master'2023-04-04T20:57:51ZDanylo Vanin (EPAM)Merge branch 'fix-partition-dev2' into 'master'GONRG-6850: fix tests
See merge request osdu/platform/system/partition!368
(cherry picked from commit 5b8fe748b3d012ebd580729b8fdba1c8930be660)
b969118e GONRG-6850: fix tests
52b97eb3 GONRG-6850: fix tests
4a509363 GONRG-6851: fix testsGONRG-6850: fix tests
See merge request osdu/platform/system/partition!368
(cherry picked from commit 5b8fe748b3d012ebd580729b8fdba1c8930be660)
b969118e GONRG-6850: fix tests
52b97eb3 GONRG-6850: fix tests
4a509363 GONRG-6851: fix testsM17 - Release 0.20Danylo Vanin (EPAM)Danylo Vanin (EPAM)