seismic-dms-service merge requestshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests2021-10-26T02:35:16Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/242fix: remove users only if exists2021-10-26T02:35:16ZVarunkumar Manoharfix: remove users only if existsThis MR removes users from dataset ACLs or subproject ACLs only if the user exists.
Previously, the code-behind tried removing the user from ever group in the ACLs which was sub-optimal.This MR removes users from dataset ACLs or subproject ACLs only if the user exists.
Previously, the code-behind tried removing the user from ever group in the ACLs which was sub-optimal.M10 - Release 0.13https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/248fix: during user removal, add slbclient substring to delfiserviceaccount email2021-10-28T19:47:25ZVarunkumar Manoharfix: during user removal, add slbclient substring to delfiserviceaccount emailEntitlements-svc adds `slbclient` to email address belonging to a `delfiserviceaccount` during group addition.
So during user removal, the input email needs to contain `slbclient`substring too for `delfiserviceaccount`.
For instance, i...Entitlements-svc adds `slbclient` to email address belonging to a `delfiserviceaccount` during group addition.
So during user removal, the input email needs to contain `slbclient`substring too for `delfiserviceaccount`.
For instance, if the useremail for deletion is `5dca4c83723e4f3182134@delfiserviceaccount.com`, this MR updates the useremail to `5dca4c83723e4f3182134.slbclient@delfiserviceaccount.com`M10 - Release 0.13https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/258fix: Ibm sha commit change2021-11-03T13:16:44ZAshwani Pandeyfix: Ibm sha commit changeIbm sha commit changeIbm sha commit changeM10 - Release 0.13Ashwani PandeyAshwani Pandeyhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/268fix: updating json-schema to prevent vulnerability issue (MR2)2021-11-17T18:54:07Z[MSFT] Sally Ransomfix: updating json-schema to prevent vulnerability issue (MR2)Take TWO 🎬
This update to json-schema resolves the issue found (below) by Component Governance
json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
![json-schema_issue]...Take TWO 🎬
This update to json-schema resolves the issue found (below) by Component Governance
json-schema is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
![json-schema_issue](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/uploads/96b3d13cf60b2afabd73464beec41f8f/json-schema_issue.png)M10 - Release 0.13[MSFT] Sally Ransom[MSFT] Sally Ransomhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/269chore: Updated NOTICE per json-schema and python-pip changes2021-11-17T19:01:11Z[MSFT] Sally Ransomchore: Updated NOTICE per json-schema and python-pip changesSince the json-schema and python-pip dependencies were update, the NOTICE should be updated too.Since the json-schema and python-pip dependencies were update, the NOTICE should be updated too.M10 - Release 0.13[MSFT] Sally Ransom[MSFT] Sally Ransomhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/270fix: updating json-schema requirement for jsprim to prevent vulnerability issue2021-11-17T23:46:10Z[MSFT] Sally Ransomfix: updating json-schema requirement for jsprim to prevent vulnerability issueAlas! There was one more json-schema that was causing problems... in the requirements list for jsprim. It's updated to 4.0 now.Alas! There was one more json-schema that was causing problems... in the requirements list for jsprim. It's updated to 4.0 now.M10 - Release 0.13[MSFT] Sally Ransom[MSFT] Sally Ransomhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/276fix: added user info translation in dataset list endpoint2021-11-25T11:25:23ZDiego Moltenifix: added user info translation in dataset list endpointadded user info translation in dataset list endpointadded user info translation in dataset list endpointM10 - Release 0.13https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/267Draft: fix: ensure the AAD Pod Identity get registered before starting the se...2021-12-20T11:02:06ZDiego MolteniDraft: fix: ensure the AAD Pod Identity get registered before starting the serviceAdded a method to ensure the AAD Pod Identity get registered before starting the serviceAdded a method to ensure the AAD Pod Identity get registered before starting the serviceM10 - Release 0.13https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/281refactor: server class code review2021-12-28T16:30:03ZDiego Moltenirefactor: server class code review- Added missing types
- removed redundant code while initializing the server (using the alternative type)
- moved initialization of header propagation on application start
- moved the fix on swagger-ui on application start.
- removed unu...- Added missing types
- removed redundant code while initializing the server (using the alternative type)
- moved initialization of header propagation on application start
- moved the fix on swagger-ui on application start.
- removed unused export
- removed temporary audience log added x SLB internal code transaction
- remove unused call logger metric on content-sizeM10 - Release 0.13https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/303Draft: fix: azure comsos DB redesign2022-01-24T09:11:12ZDiego MolteniDraft: fix: azure comsos DB redesignThe existing design of cosmos DB could not meet the required performances.
All datasets that belong to the same subproject are stored with/under the same physical partition key. A physical partition set a limit of 10k RU/s (cannot be mod...The existing design of cosmos DB could not meet the required performances.
All datasets that belong to the same subproject are stored with/under the same physical partition key. A physical partition set a limit of 10k RU/s (cannot be modified).
To enable cosmos horizontal scaling and higher RU/s the DB has been redesigned so every entity (tenant/subproject/dataset/app) will have its own partition key. This will allow cosmos to spread entities across multiple phgisical partition
- tenant -> tn-<tenant_namme> (1 per partition)
- subproject -> sp-<subproject_name> (subproject belong to a tenant )
- dataset -> ds-<subprpoject_name>-<dataset_path>-<dataset_name> (datasets belong to a subproject... the subproject name is required)
- app -> app-<app_name> (apps belong to a tenant)
ref: https://docs.microsoft.com/en-us/azure/cosmos-db/partitioning-overview#choose-partitionkey
in addition, an issue has been fixed on how global tags are parsed from input requests.M10 - Release 0.13https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/335ci: added release promote stage2022-02-23T06:20:42ZWalter Dci: added release promote stageThis MR is a follow up to the reverted changes in MR !333This MR is a follow up to the reverted changes in MR !333M10 - Release 0.13David Diederichd.diederich@opengroup.orgWalter DDavid Diederichd.diederich@opengroup.org