OS Core Common - Spring 5 merge requestshttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests2024-03-19T17:14:51Zhttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/260merge with no change2024-03-19T17:14:51ZYunhua Koglinmerge with no changeM23 - Release 0.26Yunhua KoglinYunhua Koglinhttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/245Cherry-pick 'Add phrase suggestion to search query' into release/0.252023-12-12T16:04:13ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Add phrase suggestion to search query' into release/0.25**Original MR**: !242
### 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**: !242
### 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/lib/core/os-core-common/-/pipelines/new?ref=cherry-pick-for-242)M22 - Release 0.25David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/238Update FOSSA NOTICE2023-10-13T22:42:20ZDavid Diederichd.diederich@opengroup.orgUpdate FOSSA NOTICEThis MR updates the attribution file for the project (also known as the `NOTICE` file).
It is important to keep this up to date to satisfy legal requirements of dependency licenses.
We use FOSSA as the tool to scan for and detect these ...This MR updates the attribution file for the project (also known as the `NOTICE` file).
It is important to keep this up to date to satisfy legal requirements of dependency licenses.
We use FOSSA as the tool to scan for and detect these changes.M22 - Release 0.25https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/230Cherry-pick 'Added dataset admin role' into release/0.232023-09-05T12:35:22ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Added dataset admin role' into release/0.23**Original MR**: !229
### 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**: !229
### 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/lib/core/os-core-common/-/pipelines/new?ref=cherry-pick-for-229)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/229Added dataset admin role2023-09-05T11:49:42ZDeepa KumariAdded dataset admin roleDataset Admin Role to be used in Revoke URL API from dataset serviceDataset Admin Role to be used in Revoke URL API from dataset serviceM20 - Release 0.23Deepa KumariDeepa Kumarihttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/228Cherry-pick 'Allow selection of highlighted fields' into release/0.232023-08-29T04:37:17ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Allow selection of highlighted fields' into release/0.23**Original MR**: !226
### 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**: !226
### 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/lib/core/os-core-common/-/pipelines/new?ref=cherry-pick-for-226)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/224Adding expiry time for File DMS Security Enhancement2023-09-05T11:50:04ZDeepa KumariAdding expiry time for File DMS Security EnhancementRelated ADR: https://community.opengroup.org/osdu/platform/system/file/-/issues/78 and https://community.opengroup.org/osdu/platform/system/dataset/-/issues/57Related ADR: https://community.opengroup.org/osdu/platform/system/file/-/issues/78 and https://community.opengroup.org/osdu/platform/system/dataset/-/issues/57M20 - Release 0.23Deepa KumariDeepa Kumarihttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/207Cherry-pick 'Update FOSSA NOTICE' into release/0.202023-04-07T18:29:32ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Update FOSSA NOTICE' into release/0.20**Original MR**: !206
### 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**: !206
### 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/lib/core/os-core-common/-/pipelines/new?ref=cherry-pick-for-206)M17 - Release 0.20David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/206Update FOSSA NOTICE2023-04-07T18:27:57ZDavid Diederichd.diederich@opengroup.orgUpdate FOSSA NOTICEThis MR updates the attribution file for the project (also known as the `NOTICE` file).
It is important to keep this up to date to satisfy legal requirements of dependency licenses.
We use FOSSA as the tool to scan for and detect these ...This MR updates the attribution file for the project (also known as the `NOTICE` file).
It is important to keep this up to date to satisfy legal requirements of dependency licenses.
We use FOSSA as the tool to scan for and detect these changes.M17 - Release 0.20https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/205Cherry-pick 'upgrading dependencies' into release/0.202023-04-07T14:35:00ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'upgrading dependencies' into release/0.20**Original MR**: !204
### 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**: !204
### 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/lib/core/os-core-common/-/pipelines/new?ref=cherry-pick-for-204)M17 - Release 0.20David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/188Cherry-pick 'Expose Collaboration Context' into release/0.182022-12-22T23:48:13ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Expose Collaboration Context' into release/0.18**Original MR**: !183
### 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**: !183
### 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/lib/core/os-core-common/-/pipelines/new?ref=cherry-pick-for-183)M15 - Release 0.18David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/187Update FOSSA NOTICE2022-12-22T23:48:13ZDavid Diederichd.diederich@opengroup.orgUpdate FOSSA NOTICEThis MR updates the attribution file for the project (also known as the `NOTICE` file).
It is important to keep this up to date to satisfy legal requirements of dependency licenses.
We use FOSSA as the tool to scan for and detect these ...This MR updates the attribution file for the project (also known as the `NOTICE` file).
It is important to keep this up to date to satisfy legal requirements of dependency licenses.
We use FOSSA as the tool to scan for and detect these changes.M15 - Release 0.18https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/186Aws integration merge (updating NOTICE)2022-12-22T23:49:20ZMichael SaccoAws integration merge (updating NOTICE)M15 - Release 0.18Michael SaccoMichael Saccohttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/185Aws integration merge2022-12-22T23:49:55ZMichael SaccoAws integration mergeM15 - Release 0.18Okoun-Ola Fabien HouetoMichael SaccoOkoun-Ola Fabien Houetohttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/180Cherry-pick 'fix whitesource issues' into release/0.172022-12-22T23:48:13ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'fix whitesource issues' into release/0.17**Original MR**: !179
### 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**: !179
### 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/lib/core/os-core-common/-/pipelines/new?ref=cherry-pick-for-179)M14 - Release 0.17David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/166spring-webmvc upgrade2022-09-16T02:12:10ZMorris Estepaspring-webmvc upgradeupgrade spring-webmvc libraryupgrade spring-webmvc libraryM13 - Release 0.16Morris EstepaMorris Estepahttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/157Update jackson 3rd party library versions2023-08-18T13:06:55ZMorris EstepaUpdate jackson 3rd party library versionscommit a143405d
Author: Sutton <suttonsp@147dda3a90de.ant.amazon.com>
Date: Fri Jan 15 2021 16:26:24 GMT-0600 (Central Standard Time)
Updated domains to be a list
commit 7902b04f
Author: Sutton <suttonsp@147dda3a90de.ant.amazo...commit a143405d
Author: Sutton <suttonsp@147dda3a90de.ant.amazon.com>
Date: Fri Jan 15 2021 16:26:24 GMT-0600 (Central Standard Time)
Updated domains to be a list
commit 7902b04f
Author: Sutton <suttonsp@147dda3a90de.ant.amazon.com>
Date: Fri Jan 15 2021 14:41:29 GMT-0600 (Central Standard Time)
Adding ResponseHeadersFactory, deprecating ResponseHeadersM12 - Release 0.15Morris EstepaMorris Estepahttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/154Adding Two new Spatial Filters per CRS ADR2022-09-15T10:17:55ZSpencer Suttonsuttonsp@amazon.comAdding Two new Spatial Filters per CRS ADRChange related to ADR: https://community.opengroup.org/osdu/platform/system/home/-/issues/94Change related to ADR: https://community.opengroup.org/osdu/platform/system/home/-/issues/94M12 - Release 0.15Spencer Suttonsuttonsp@amazon.comSpencer Suttonsuttonsp@amazon.comhttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/143Updating NOTICE2023-08-18T13:07:05ZDavid Diederichd.diederich@opengroup.orgUpdating NOTICEM11 - Release 0.14David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/merge_requests/139Updating NOTICE2022-12-22T23:56:16ZDavid Diederichd.diederich@opengroup.orgUpdating NOTICENow that fossa-with-cache logic is activated, this updates the NOTICE to use the formatted formatNow that fossa-with-cache logic is activated, this updates the NOTICE to use the formatted formatM10 - Release 0.13David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.org