seismic-dms-service issueshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues2024-03-05T01:03:53Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/124[IBM] fix new cloudant driver/lib2024-03-05T01:03:53ZAnuj Gupta[IBM] fix new cloudant driver/libFix : Unit Test Required
- [x] if no db created. initDB
- [x] existing record get (no migration)
- [x] save new record and get
- [x] put and patch
- [x] delete
- [x] runQuery
Branch : [ibm-cloudant-result](https://community.opengroup.or...Fix : Unit Test Required
- [x] if no db created. initDB
- [x] existing record get (no migration)
- [x] save new record and get
- [x] put and patch
- [x] delete
- [x] runQuery
Branch : [ibm-cloudant-result](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/commits/fix/ibm-cloudant-result)M23 - Release 0.26Isha KumariIsha Kumari2024-01-26https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/59What are some of the variables in tests/e2e/postman_env.json and where does o...2022-06-16T09:21:25ZKamlesh TodaiWhat are some of the variables in tests/e2e/postman_env.json and where does one find the values for them?Looking at the following file
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/blob/master/app/sdms/tests/e2e/postman_env.json
I am not sure what these variables a...Looking at the following file
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/blob/master/app/sdms/tests/e2e/postman_env.json
I am not sure what these variables are and where does one get the values for them
the list of the variables that need clarification and also where to get to get the values for them?
**SVC_API_KEY**
**STOKEN** is it id_token, access_token or refresh_token?
**DE_APP_KEY**
**VCS_Provider**M12 - Release 0.15https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/33Inconsistent behavior across CSPs - while Registering/creating seismic-dms te...2023-03-27T19:24:28ZKamlesh TodaiInconsistent behavior across CSPs - while Registering/creating seismic-dms tenantPOST .../tenant​/{tenantid} Register a seismic-dms tenant. The API document says Required roles: seistore.system.admin
Is this role granted to the average user/tester or does it require a user with elevated permissions?
What I ...POST .../tenant​/{tenantid} Register a seismic-dms tenant. The API document says Required roles: seistore.system.admin
Is this role granted to the average user/tester or does it require a user with elevated permissions?
What I am noticing is that in
**For AWS**,
I am able to register the new seismic-dms tenant, where else
**For IBM and Azure**,
I am not able to do that. I get the message - [seismic-store-service] The tenant name must match the data partition ID 'opendes'
**For GCP** -
**I have to pass the id_token instead of access_token** and when I do that I get the message - [entitlement-service] 401 - "{\"code\":401,\"reason\":\"Obtaining user info issue\",\"message\":\"Not valid token provided\"}" - appears that when I pass the id_token, the entitlement API is running into problem and if I pass the access_token then I get Unexpected token k in JSON at position 0
@ChrisZhang @manishk @anujgupta @Kateryna_Kurach @Wibben @sachahttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/13Enable CI CD pipeline for IBM siesmic store svc2021-02-11T06:36:25ZAnuj GuptaEnable CI CD pipeline for IBM siesmic store svcEnable CI CD pipeline for IBMEnable CI CD pipeline for IBMAnuj GuptaAnuj Guptahttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/7Data Ecosystem Service Host refactoring2021-02-11T16:29:58ZAnuj GuptaData Ecosystem Service Host refactoringThere is a variable DES_SERVICE_HOST at below code which assumes that all the data ecosystem services (storage, entitlement, legal) should have same base url which may not be the case in ibm implementation and also reduces the flexibilit...There is a variable DES_SERVICE_HOST at below code which assumes that all the data ecosystem services (storage, entitlement, legal) should have same base url which may not be the case in ibm implementation and also reduces the flexibility to orchestrate services for debugging.
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/blob/master/src/cloud/config.ts#L156
As of now we have raised below MR but may have to make change in core for above said issue.
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/1
cc: @dsouzawalterDiego MolteniDiego Molteni