Policy merge requestshttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests2023-09-05T19:30:41Zhttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/421Cherry-pick 'Release notes update' into release/0.232023-09-05T19:30:41ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Release notes update' into release/0.23**Original MR**: !417
### 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**: !417
### 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/policy/-/pipelines/new?ref=cherry-pick-for-417)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/420Cherry-pick: Merge branch 'doc-update' into 'master'2023-09-04T18:43:32ZChad LeongCherry-pick: Merge branch 'doc-update' into 'master'documentation update
See merge request osdu/platform/security-and-compliance/policy!415
(cherry picked from commit 380d897b8dd6af45a87a3d3f26ce17039013724a)
8870a55a documentation update
51cd29cf release notes updatedocumentation update
See merge request osdu/platform/security-and-compliance/policy!415
(cherry picked from commit 380d897b8dd6af45a87a3d3f26ce17039013724a)
8870a55a documentation update
51cd29cf release notes updateM20 - Release 0.23https://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/419Cherry-pick 'documentation update for M20' into release/0.232023-09-04T18:42:16ZChad LeongCherry-pick 'documentation update for M20' into release/0.23**Original MR**: !414
### 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**: !414
### 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/policy/-/pipelines/new?ref=cherry-pick-for-414)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/418another small doc update2023-09-05T17:10:12ZShane Hutchinsanother small doc updateM20 - Release 0.23Shane HutchinsShane Hutchinshttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/417Release notes update2023-09-05T17:09:57ZShane HutchinsRelease notes updateUpdating release notes for M20 and noting issue (memory leak) in M18 and M19.Updating release notes for M20 and noting issue (memory leak) in M18 and M19.M20 - Release 0.23Shane HutchinsShane Hutchinshttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/416Cherry-pick 'Multi partition update' into release/0.232023-09-05T12:37:42ZSrinivasan NarayananCherry-pick 'Multi partition update' into release/0.23**Original MR**: !412
### 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**: !412
### 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/policy/-/pipelines/new?ref=cherry-pick-for-412)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/415documentation update2023-09-04T18:42:41ZShane Hutchinsdocumentation update- updating release notes
- translate doc update- updating release notes
- translate doc updateM20 - Release 0.23Shane HutchinsShane Hutchinshttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/414documentation update for M202023-09-04T18:41:54ZShane Hutchinsdocumentation update for M20- Updating documentation for M20 release.- Updating documentation for M20 release.M20 - Release 0.23Shane HutchinsShane Hutchinshttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/413Cherry-pick 'Add python dependencies' into release/0.232023-09-01T15:35:24ZSrinivasan NarayananCherry-pick 'Add python dependencies' into release/0.23**Original MR**: !411
### 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**: !411
### 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/policy/-/pipelines/new?ref=cherry-pick-for-411)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/412Multi partition update2023-09-05T08:27:17ZShane HutchinsMulti partition update- Bugfix and improvements for multi-partition support and azure build
- New diagnostic API (off by default) for memory leak and slow down overtime support- Bugfix and improvements for multi-partition support and azure build
- New diagnostic API (off by default) for memory leak and slow down overtime supportM20 - Release 0.23Shane HutchinsShane Hutchinshttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/411Add python dependencies2023-09-01T11:36:36Zsaketh somarajuAdd python dependenciesAdd `psutil` and `ruamel.yaml` dependencies to fix azure_deployAdd `psutil` and `ruamel.yaml` dependencies to fix azure_deployM20 - Release 0.23saketh somarajusaketh somarajuhttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/410GONRG-7679: update policy bootstrap2023-09-27T10:51:31ZYauheni Rykhter (EPAM)GONRG-7679: update policy bootstrapM21 - Release 0.24Yauheni Rykhter (EPAM)Yauheni Rykhter (EPAM)https://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/409Cherry-pick 'initial commit in multi-partition support' into release/0.232023-08-30T05:04:40ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'initial commit in multi-partition support' into release/0.23**Original MR**: !403
### 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**: !403
### 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/policy/-/pipelines/new?ref=cherry-pick-for-403)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/408update release notes for issue 101 and 1032023-09-05T08:26:52ZSrabana Guhaupdate release notes for issue 101 and 103M20 - Release 0.23Shane HutchinsShane Hutchinshttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/407Merge branch 'ibm-image-fix' into 'master'2023-08-22T06:53:06ZIsha KumariMerge branch 'ibm-image-fix' into 'master'Ibm image fix
See merge request osdu/platform/security-and-compliance/policy!397
(cherry picked from commit 049a77d01edd20449b25aeba8605e43fc813ab2b)
c03ccd3d Add new directory
d99721e6 Add new fileIbm image fix
See merge request osdu/platform/security-and-compliance/policy!397
(cherry picked from commit 049a77d01edd20449b25aeba8605e43fc813ab2b)
c03ccd3d Add new directory
d99721e6 Add new fileIsha KumariIsha Kumarihttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/406Merge branch 'ibm-image-fix' into 'master'2023-08-22T05:56:24ZIsha KumariMerge branch 'ibm-image-fix' into 'master'Ibm image fix
See merge request osdu/platform/security-and-compliance/policy!397
(cherry picked from commit 049a77d01edd20449b25aeba8605e43fc813ab2b)
c03ccd3d Add new directory
d99721e6 Add new fileIbm image fix
See merge request osdu/platform/security-and-compliance/policy!397
(cherry picked from commit 049a77d01edd20449b25aeba8605e43fc813ab2b)
c03ccd3d Add new directory
d99721e6 Add new fileIsha KumariIsha Kumarihttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/405AWS Merge Dev Into Master2023-08-18T19:50:23ZGuillaume CailletAWS Merge Dev Into MasterM20 - Release 0.23Guillaume CailletGuillaume Caillethttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/404Add option in Translate Api to construct elastic search subquery in search re...2023-08-22T18:09:04ZSrabana GuhaAdd option in Translate Api to construct elastic search subquery in search rego policyCloses issue https://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/issues/103Closes issue https://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/issues/103M20 - Release 0.23https://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/403initial commit in multi-partition support2023-08-29T20:29:29ZShane Hutchinsinitial commit in multi-partition support- Bugfix memory leak / Performance issue over time fix https://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/issues/93
- Added new response header X-Process-Time. This new header contains the time in seconds that...- Bugfix memory leak / Performance issue over time fix https://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/issues/93
- Added new response header X-Process-Time. This new header contains the time in seconds that it took to process the request and generate a response in policy service.
- /config defect fix
- /config mask https://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/issues/109
- Initial commit for /tenant APIs - multi-partition support
- Cache settings updatable via environment variables
- Documentation updates
- Updated responses when Input doesn't match criteria for translate API
- Updated libraries for pydantic and FastAPIM20 - Release 0.23Shane HutchinsShane Hutchinshttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/merge_requests/402test scenarios with input data2023-08-18T12:21:43ZSrabana Guhatest scenarios with input dataM20 - Release 0.23