seismic-dms-service merge requestshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests2022-06-17T17:50:08Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/404Add Dockerfile and Feed Changes2022-06-17T17:50:08ZElizabeth HalperAdd Dockerfile and Feed ChangesIn order to get the file metadata service to work on Azure, we needed to be able to access the segy-python library. We added it to an ADO feed and updated the Dockerfile and configs accordingly.In order to get the file metadata service to work on Azure, we needed to be able to access the segy-python library. We added it to an ADO feed and updated the Dockerfile and configs accordingly.Elizabeth HalperElizabeth Halperhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/92added reason for 423 error message2021-05-18T16:23:06ZDiego Molteniadded reason for 423 error messageAdded Reason Code to the 423 Error Message. Clients applications can better detect the status of the lock error and correctly handle their flow. The Reason is a string code placed at the end to the error message an has this form:
`"[" +...Added Reason Code to the 423 Error Message. Clients applications can better detect the status of the lock error and correctly handle their flow. The Reason is a string code placed at the end to the error message an has this form:
`"[" + RCODE(fixed-tag) + ":" + REASON-CODE(2-char-code) + TTL(sec-number) + "]"`
The REASON-CODE possible values are:
* WL: The dataset is write locked
* RL: The dataset is read locked
* CL: The dataset can't be locked (lock cache mutex can't be acquired)
* CU: The dataset can't be unlocked (lock cache mutex can't be released)
For example:
`[seismic-store] The dataset is write locked [RCODE:WL3600]`https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/82added reason for 423 error message2021-05-18T16:14:36ZDiego Molteniadded reason for 423 error messageAdded Reason Code to the 423 Error Message. Clients applications can better detect the status of the lock error and correctly handle their flow. The Reason is a string code placed at the end to the error message an has this form:
`"[" +...Added Reason Code to the 423 Error Message. Clients applications can better detect the status of the lock error and correctly handle their flow. The Reason is a string code placed at the end to the error message an has this form:
`"[" + RCODE(fixed-tag) + ":" + REASON-CODE(2-char-code) + TTL(sec-number) + "]"`
The REASON-CODE possible values are:
- WL: The dataset is write locked
- RL: The dataset is read locked
- CL: The dataset can't be locked (lock cache mutex can't be acquired)
- CU: The dataset can't be unlocked (lock cache mutex can't be released)
For example:
`[seismic-store] The dataset is write locked [RCODE:WL3600]`
swagger documentation updated.https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/380Add M8 Changes to M10-Master2022-09-07T16:48:53ZElizabeth HalperAdd M8 Changes to M10-MasterThis merges m8 changes into the m10 branchThis merges m8 changes into the m10 branchElizabeth HalperElizabeth Halperhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/107Add node selector2021-08-05T09:51:53ZDzmitry_Paulouski (slb)Add node selectorAll Submissions:
[YES] Have you followed our code review guidelines?
[YES] Have you added an explanation of what your changes do and why you'd like us to include them?
[NO] I have updated the documentation accordingly.
[NA] I have adde...All Submissions:
[YES] Have you followed our code review guidelines?
[YES] Have you added an explanation of what your changes do and why you'd like us to include them?
[NO] I have updated the documentation accordingly.
[NA] I have added tests to cover my changes.
[YES] All new and existing tests passed.
[YES] My code follows the code style of this project.
[YES] I ran lint checks locally prior to submission.
What is the current behavior?
Currently, we have only one node pool for services and system workloads.
What is the new behavior?
We are going to move workloads to a new node pool with enabled autoscaling. Here you can find the details:
Issue link
Does this introduce a breaking change?
[NO]
This change has a strong dependency on the following MR and should be merged only after it:
osdu/platform/deployment-and-operations/infra-azure-provisioning!324M8 - Release 0.11Dzmitry_Paulouski (slb)Dzmitry_Paulouski (slb)https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/852Add the deletion project and refactored the Sidecar to include the new projec...2023-08-24T09:19:04ZLaura DamianAdd the deletion project and refactored the Sidecar to include the new project for handling deletion## Type of change
- [ ] Bug Fix
- [x] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [x] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [x] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [x] Yes
## Have you set the target Milestone?
- [x] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [x] No
- [ ] Yes
## Updates description?
> Update this part with a description of your changeshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/857Add the locks2023-08-29T13:43:29ZLaura DamianAdd the lockshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/600Az/sk cherry pick changes2023-01-23T09:11:07Zshivani karipeAz/sk cherry pick changesshivani karipeshivani karipehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/783Az/sk convergence tests2023-07-13T08:20:08Zshivani karipeAz/sk convergence tests## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [ ] Yes
## Have you set the target Milestone?
- [ ] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ ] Yes
## Updates description?
> Update this part with a description of your changesshivani karipeshivani karipehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/781Az/sk convergence tests2023-07-05T08:21:40Zshivani karipeAz/sk convergence tests## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
## Does this introduce a change in the core logic?
- [X] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
## Does this introduce a change in the core logic?
- [X] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [X ] No
- [ ] Yes
## Have you set the target Milestone?
- [X] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [X] No
- [ ] Yes
## Updates description?
> Update this part with a description of your changesshivani karipeshivani karipehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/341build: Trusted rising/metric2022-03-01T22:43:22ZRishabh Singhbuild: Trusted rising/metrichttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/546Change PAT to Up to Date Value2022-11-02T01:16:27ZElizabeth HalperChange PAT to Up to Date Valuehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/481Cherry-pick 'ci: update alpine version to fix busybox vulnerability' into rel...2022-08-12T21:35:35ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'ci: update alpine version to fix busybox vulnerability' into release/0.16Original MR: !444Original MR: !444M13 - Release 0.16David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/1046Cherry-pick 'fix: split batchclient delete request into multiple' into releas...2023-12-20T11:01:48ZRashaad GrayCherry-pick 'fix: split batchclient delete request into multiple' into release/0.25**Original MR**: !1045
### 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 incorporat...**Original MR**: !1045
### 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.M22 - Release 0.25Rashaad GrayRashaad Grayhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/389Cherry-pick "fix: update sas user delegation key expiry time" into release/0.142022-05-06T08:40:32ZSacha BrantsCherry-pick "fix: update sas user delegation key expiry time" into release/0.14M12 - Release 0.15https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/870cherry pick MR 861 to m16 master branch2023-08-24T16:18:02Zshivani karipecherry pick MR 861 to m16 master branch## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ * ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ * ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation,...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ * ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ * ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ * ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [ * ] Yes
## Have you set the target Milestone?
- [ ] No
- [ * ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ * ] Yes
## Updates description?
> Update this part with a description of your changes
- This merge request addresses the problem of failing unit tests in the file metadata.
- It adjusts the "allow failure" setting to false, enhancing performance and preparing for potential challenges if the pipeline fails in the future.
parent MR link: [861](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/861)shivani karipeshivani karipehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/408chore: reduce usage of shared cache2022-08-12T05:24:50ZDiego Moltenichore: reduce usage of shared cacheThis change will reduce the usage of the shared cache in SDSM.
Meta information and validation will be locally cached to improve overall performances.
1. Tenant Metadata
- accessed at each call to SDMS
- TTL 1h, no changes to service b...This change will reduce the usage of the shared cache in SDSM.
Meta information and validation will be locally cached to improve overall performances.
1. Tenant Metadata
- accessed at each call to SDMS
- TTL 1h, no changes to service behavior
2. Exchanged Token
- accessed only in case token is required to be exchanged with a different audience
- TTL 5m, no changes to service behavior
3. CCM User Association
- accessed every time dataset metadata is retrieved
- TTL 1h, no changes to service behavior
4. Legal Tag Validation
- accessed at each call to SDMS
- TTL 1h, no changes to service behavior
5. Azure Storage access keys and configurations
- accessed every time a storage operation is required (create subproject / get storage access token)
- TTL 1h, no changes to service behavior
6. Azure Cosmos access keys and configurations
- accessed every time a dataset is created, retrieved, or listed
- TTL 1h, no changes to service behavior
7. Entitlement Authorization Validation
- accessed at each call to SDMS
- TTL 1m, no changes to service behavior
8. Subproject Metadata
- accessed at each call to SDMS
- TTL 60s, introduce eventual consistency on patch operation
9. AWS tenant ID from partition ID
- accessed at each call to SDMS
- TTL 1h, no changes to service behaviorM14 - Release 0.17Diego MolteniDiego Moltenihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/764chore: remove @cloudant/cloudant and regenerate npm shrinkwrap file2023-12-08T15:18:49ZDaniel Carpenterchore: remove @cloudant/cloudant and regenerate npm shrinkwrap file## Type of change
- [X] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
## Does this introduce a change in the core logic?
- [X] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ...## Type of change
- [X] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
## Does this introduce a change in the core logic?
- [X] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [ ] GCP
- [X] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [X] Yes
## Have you set the target Milestone?
- [X] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [X] No
- [ ] Yes
## Updates description?
@cloudant/cloudant is deprecated and has security issues. Removing from Azure m16 branch and will file issue for IBM to migrate to new library on master.Daniel CarpenterDaniel Carpenterhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/415chore Trigger check community variables2022-06-09T11:50:57ZSiarhei Symanovich (EPAM)chore Trigger check community variableschore Trigger check community variableschore Trigger check community variablesSiarhei Symanovich (EPAM)Siarhei Symanovich (EPAM)https://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 Ransom