seismic-dms-service merge requestshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests2023-10-04T08:38:22Zhttps://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/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/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/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/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/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/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/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/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/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/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/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/394feat: Implement more apis on File Metadata Service2022-05-04T12:42:34ZDuo Chenfeat: Implement more apis on File Metadata Service1. Update README.md by removing all the information related to slb.
2. Modify the OpenAPI to group the apis
3. Add two more APIs: get_scaledTraceHeaders and get_rawTraceHeaders1. Update README.md by removing all the information related to slb.
2. Modify the OpenAPI to group the apis
3. Add two more APIs: get_scaledTraceHeaders and get_rawTraceHeadersM12 - Release 0.15https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/1071feat: implement endpoint id logging2024-02-08T16:41:21ZKonstantin Khottchenkovfeat: implement endpoint id logging## 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?
Implement simple endpoint id logging for SDMS-v4M23 - Release 0.26https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/674feat: implemented query parameters in list dataset endpoint2023-08-01T07:39:28ZGiorgi Baramidzefeat: implemented query parameters in list dataset endpointlist endpoint now supports sql-query-style parameter and search parameterlist endpoint now supports sql-query-style parameter and search parameterM20 - Release 0.23https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/791feat: Implement correlation-id in SDMS traces log2023-07-10T16:00:11ZJason Wangfeat: Implement correlation-id in SDMS traces log## 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?
> I have to create a new Merge Request due to a merge conflict.M20 - Release 0.23Jason WangJason Wanghttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/535feat: Ibm arn change2022-10-07T05:40:28ZWalter Dfeat: Ibm arn changeM15 - Release 0.18Walter DWalter Dhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/1093feat: [GONRG-9211] Added labels to gc helm2024-03-19T17:06:19ZDanylo Vanin (EPAM)feat: [GONRG-9211] Added labels to gc helm## 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
- [ ] IBMM23 - Release 0.26Danylo Vanin (EPAM)Danylo Vanin (EPAM)https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/937feat: [GONRG-7917] added replicas variable in helm2023-10-13T10:56:35ZAleksandr Primachenko [EPAM / GCP]feat: [GONRG-7917] added replicas variable in helm## 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
- [X] 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 changesM21 - Release 0.24Aleksandr Primachenko [EPAM / GCP]Aleksandr Primachenko [EPAM / GCP]https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/623feat: GONRG-6259: Add osdu google2023-07-24T15:37:29ZYan Sushchynski (EPAM)feat: GONRG-6259: Add osdu googleAdd the Google cloud implementation, which follows OSDU approaches.
The main difference from the "old" Google implementation:
1. Don't create a new bucket for each new subproject
2. Add support of an access token (Google access tokens a...Add the Google cloud implementation, which follows OSDU approaches.
The main difference from the "old" Google implementation:
1. Don't create a new bucket for each new subproject
2. Add support of an access token (Google access tokens are not JWT)
4. Add the room for future improvements for Multipartition
4. The service will use the `data-partition-id` value instead of the `gcp-id`, the gcp-id should be hidden from any user but Ops and DevsM19 - Release 0.22