seismic-dms-service merge requestshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests2023-01-12T16:17:56Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/595feat: increase code coverage2023-01-12T16:17:56ZJason Wangfeat: increase code coverageincreased the code coverage for unit test.increased the code coverage for unit test.M16 - Release 0.19Jason WangJason Wanghttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/756feat: logging improvements2023-06-20T15:26:08ZDaniel Carpenterfeat: logging improvements## Type of change
- [ ] Bug Fix
- [X] 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
- [X] 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
- [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?
Improve logging in SDMS, add missing serialization, logging prefixes, and trace statements. Resolving issues like logging "{"code"=>500, "message"=>"[seismic-store-service] **[object Object]**", "status"=>"UNKNOWN"}"Daniel CarpenterDaniel Carpenterhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/831feat: ls as post2023-08-07T14:07:56ZDiego Moltenifeat: ls as post## 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
- [ ] 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?
- [ ] No
- [X] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [X] Yes
## Updates description?
> Added POST endpoint interface for the LS methodM20 - Release 0.23Diego MolteniDiego Moltenihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/598feat: make SDMS-V4 service dynamic by removing the hardcoded schema data from...2023-01-13T14:45:36ZRashaad Grayfeat: make SDMS-V4 service dynamic by removing the hardcoded schema data from the servicefeat: make service dynamic by removing the hardcoded schema data from the servicefeat: make service dynamic by removing the hardcoded schema data from the serviceM16 - Release 0.19Rashaad GrayRashaad Grayhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/936feat: make task queues for Azure operations abstract2023-11-28T12:49:52ZKonstantin Gukovfeat: make task queues for Azure operations abstract## 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?
- [ ] No
- [x] Yes
## Updates description?
This abstraction allows to:
- add new task queue technologies by adding more `ITaskQueueWorker`s (e.g. support task queues based on Azure Storage Queue or Service Bus)
- subscribe to multiple queues at the same time by just adding more `HostedService`s (e.g. to smoothly migrate from one queue to another)
- add new task types to execute by adding more `ITaskExecutor`s (curently we only have Delete operations)M22 - Release 0.25Maggie SalakIzabela KulakowskaMaggie Salakhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/1008feat: merge aws code to gitlab2023-11-22T01:57:16ZYunhua Koglinfeat: merge aws code to gitlab## Type of change
- [X] Bug Fix
- [ ] 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
- [X] Bug Fix
- [ ] 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?
- [X] AWS
- [ ] Anthos
- [ ] 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?
- [ ] No
- [X] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [X] Yes
## Updates description?
> Update this part with a description of your changesM22 - Release 0.25Guillaume CailletGuillaume Caillethttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/215feat: merge filemetadata service2021-09-29T12:23:40ZVladimir Moiseevfeat: merge filemetadata servicemerge seismic file meta data service into seismic dmsmerge seismic file meta data service into seismic dmsM9 - Release 0.12Diego MolteniVladimir MoiseevDiego Moltenihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/435feat: Migrate the segysdk_python from ADO to OSDU2022-07-13T14:34:53ZDuo Chenfeat: Migrate the segysdk_python from ADO to OSDUMigrate the segysdk_python from ADO to OSDU.Migrate the segysdk_python from ADO to OSDU.M13 - Release 0.16Duo ChenDuo Chenhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/1101feat: move cloudProvider to configmap2024-03-20T15:12:02ZMykola Ronik [EPAM / GCP]feat: move cloudProvider to configmap## 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
- [ ] Azure
- [x] 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?
- [ ] No
- [x] Yes
## Updates description?
> moved cloudConfig to configmapM23 - Release 0.26Mykola Ronik [EPAM / GCP]Mykola Ronik [EPAM / GCP]https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/486feat: openzgy endpoint for converting zgy file to bingrid2022-08-18T08:09:34ZPanagiotis Kraniotisfeat: openzgy endpoint for converting zgy file to bingridopenzgy endpoint for converting zgy file to bingrid, using the openzgy wrapperopenzgy endpoint for converting zgy file to bingrid, using the openzgy wrapperM14 - Release 0.17Panagiotis KraniotisPanagiotis Kraniotishttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/250feat: parametrize user claim identifiers using env vars and add user associat...2021-11-09T10:48:08ZVarunkumar Manoharfeat: parametrize user claim identifiers using env vars and add user association service provider factoryThis MR accomplishes the following
1. Introduces the ability to pass principal identifiers via environment variables. For invoking entitlements-svc APIs, this principal identifier is read from the environment variable `USER_ID_CLAIM_FOR...This MR accomplishes the following
1. Introduces the ability to pass principal identifiers via environment variables. For invoking entitlements-svc APIs, this principal identifier is read from the environment variable `USER_ID_CLAIM_FOR_ENTITLEMENTS_SVC` and for all others it is read from `USER_ID_CLAIM_FOR_SDMS`
2. Provides an ability to obtain user-association-service-provider using a factory. Using typescript decorators and corresponding identifiers, user-association-svc-providers can now be extended. The runtime using the environment variable `USER_ASSOCIATION_SVC_PROVIDER` can instantiate the right provider. For instance, when the environment variable `USER_ASSOCIATION_SVC_PROVIDER` is set to `slb-ccm-internal`, the associated implementation of the user-association-svc interaction can be used by the consumer.M10 - Release 0.13https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/904feat: precommit dotnet checks2023-10-04T08:38:22ZKonstantin Gukovfeat: precommit dotnet checks## 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
- [ ] 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?
- [ ] No
- [x] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [x] Yes
## Updates description?
> Update this part with a description of your changesM21 - Release 0.24https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/918feat: Refactor for generic operation and small improvements(authorization che...2023-10-02T11:28:01ZLaura Damianfeat: Refactor for generic operation and small improvements(authorization check, paths check, add the id of the user that created the deletion operation)## 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 changesLaura DamianLaura Damianhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/446feat: Remove favicon because it is not licensed2022-07-27T19:37:50ZDuo Chenfeat: Remove favicon because it is not licensedRemove favicon because it is not licensed.Remove favicon because it is not licensed.M13 - Release 0.16https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/1026feat: remove legacy subfolders query and feature flag2023-12-06T09:04:29ZMaggie Salakfeat: remove legacy subfolders query and feature flag## 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?
- [ ] No
- [x] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [x] Yes
## Updates description?
> Update this part with a description of your changesM23 - Release 0.26Maggie SalakMaggie Salakhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/838feat: Rename sa for Seismic2023-08-18T10:24:28ZYauheny Boika[EPAM / GCP]feat: Rename sa for Seismic## 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
- [ ] Azure
- [X] 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 changesM20 - Release 0.23https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/563feat: replace ajv with jsonschem for future api schema validation2022-11-22T20:00:08ZRashaad Grayfeat: replace ajv with jsonschem for future api schema validationreplace ajv with jsonschem for future api schema validation. ajv would not allow new schemas to validate because of bugreplace ajv with jsonschem for future api schema validation. ajv would not allow new schemas to validate because of bugM16 - Release 0.19https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/490feat: replace deprecated request-promise npm package2022-09-02T15:34:01ZMario Murillofeat: replace deprecated request-promise npm packagefeat: replace deprecated request-promise npm packagefeat: replace deprecated request-promise npm packageM14 - Release 0.17https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/282feat: schema management for openzgy and segy datasets2021-12-17T04:29:04ZVarunkumar Manoharfeat: schema management for openzgy and segy datasetsThis MR accomplishes the following
1. Schemas for `openzgy_v1` and `segy_v1` are imported from the schema repo [here](https://community.opengroup.org/osdu/data/data-definitions/-/tree/master/Generated/dataset)
2. Schema managers for `s...This MR accomplishes the following
1. Schemas for `openzgy_v1` and `segy_v1` are imported from the schema repo [here](https://community.opengroup.org/osdu/data/data-definitions/-/tree/master/Generated/dataset)
2. Schema managers for `seismicmeta`, `openzgy_v1` and `segy_v1` are added. All of the logic to validate input on a schema is abstracted into respective schema manager types
3. Dataset `register`, `patch` methods now uses a common function to add defaults for the storage schema record
4. Dataset `get` method is updated to apply schema transforms on respective schema types. Multiple data transformers can now be chained and the output can be returned to the client in the supported schema type. All of the logic to perform these schema transforms are encapsulated in respective schema manager types.
5. Storage record for a particular version can be retrieved by passing `record-version` query parameter to the dataset `GET` method
6. Postman E2E tests are updated for dataset operations using `seismicmeta`, `openzgy_v1` and `segy_v1`
7. OpenAPI yaml documentation updates to import the schemas directly from sdms codebaseM10 - Release 0.13https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/420feat: SDDMS-V4 implementation2022-07-29T09:43:03ZVarunkumar Manoharfeat: SDDMS-V4 implementationThis MR implements a subset of V4 endpoints for Seismic Domain Data Management Service (SDDMS)
* These new endpoints provide the ability to
* `PUT`(register) a generic dataset
* `GET` list of datasets in a data-partition
* `...This MR implements a subset of V4 endpoints for Seismic Domain Data Management Service (SDDMS)
* These new endpoints provide the ability to
* `PUT`(register) a generic dataset
* `GET` list of datasets in a data-partition
* `GET` the generic dataset using a storage record identifier
* `DELETE` a dataset
* `GET` all the version identifier list of a dataset storage record
* `GET` a specific version of a dataset
* Additionally, endpoints for obtaining SAS tokens to upload and download the datasets are added too.
* `GET` connection string for dataset upload
* `GET` connection string to upload a specific version of a dataset
* `GET` connection string to download a dataset
* `GET` connection string to download a specific version of a dataset
* The following illustrations highlight the interactions between SDDMS and OSDU core services to register a dataset.
`PUT {{SVC_URL}}/generic/v1`
![image](/uploads/447db7444b5e498479624f86ada898e1/image.png)
* The following showcases the interactions between SDDMS and OSDU core services to GET a dataset.
`GET {{SVC_URL}}/generic/v1/record/{storage-record-id}`
![image](/uploads/cacac687b339c570f8b2b6a6e2dea0fe/image.png)
* The following illustration shows the interactions between SDDMS and OSDU to obtain a connection string for ingestion
`GET {{SVC_URL}}/connection-string/upload/record/{storage-record-id}`
`GET {{SVC_URL}}/connection-string/download/record/{storage-record-id}`
![image](/uploads/0d801051e7737a2c9b55a369b732fc0b/image.png)M13 - Release 0.16Varunkumar ManoharVarunkumar Manohar