seismic-dms-service issueshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues2023-05-02T19:11:18Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/6e2e tests - postman collection does not include tenant registration2023-05-02T19:11:18ZRucha Deshpandee2e tests - postman collection does not include tenant registrationThe postman collection used for e2e tests does not include the tenant creation which is required for e2e tests.The postman collection used for e2e tests does not include the tenant creation which is required for e2e tests.Rucha DeshpandeDiego MolteniRucha Deshpandehttps://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/51duplicate aws yml into seismic service gitlab cicd and cause staled info2023-03-24T19:33:50ZYunhua Koglinduplicate aws yml into seismic service gitlab cicd and cause staled infoCurrently seismic service gitlab cicd duplicates code from https://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/blob/master/cloud-providers/aws-global.yml and when we deploy in different stack, this staled info will fail.Currently seismic service gitlab cicd duplicates code from https://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/blob/master/cloud-providers/aws-global.yml and when we deploy in different stack, this staled info will fail.Daniel PerezDaniel Perezhttps://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/25Code linting AWS2021-03-23T16:43:04ZDiego MolteniCode linting AWScode linting to apply on aws code.
``$ tslint -c tslint.json 'src/cloud/providers/aws/**/*.ts'``code linting to apply on aws code.
``$ tslint -c tslint.json 'src/cloud/providers/aws/**/*.ts'``Rucha DeshpandeYunhua KoglinRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/21e2e test - Dataset exist / Dataset sizes validates a hardcoded list2021-03-04T22:50:06ZRucha Deshpandee2e test - Dataset exist / Dataset sizes validates a hardcoded listThis test validates a hardcoded list. Must change to environment variables OR the test script must be updated.
{
"datasets":[
"/async/dsx01",
"/a/b/c/dsx02",
"async/dsx03",
"test/dsx01",
"{{path01}}/{{dataset01}}"
]
}
Simil...This test validates a hardcoded list. Must change to environment variables OR the test script must be updated.
{
"datasets":[
"/async/dsx01",
"/a/b/c/dsx02",
"async/dsx03",
"test/dsx01",
"{{path01}}/{{dataset01}}"
]
}
Similarly, the Dataset Sizes test also validates the sizes for a hardcoded listRucha DeshpandeDiego MolteniRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/16Standardizing the OAUTH2.0 JWT payload2021-03-04T22:50:05ZBrady Spiva [AWS]Standardizing the OAUTH2.0 JWT payload## Observed behavior
The service assumes an "email" attribute is present in the JWT payload, and attempts to get the "email" attribute. See here in [/src/shared/utils.ts](https://community.opengroup.org/osdu/platform/domain-data-mgmt-ser...## Observed behavior
The service assumes an "email" attribute is present in the JWT payload, and attempts to get the "email" attribute. See here in [/src/shared/utils.ts](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/blob/master/src/shared/utils.ts#L38). There is not a standardized naming convention for this attribute, it could be "email", or "username", etc.
When using the sdutil to upload data with the `--idtoken=` parameter, the service silently handles an error, and returns a cryptic response: `'created_by'`
## Expected behavior
The service should send a request to the `/userInfo/` OAUTH2.0 endpoint to determine what this custom email attribute is, and then get it from the JWT dynamically to avoid naming conflicts between cloud providers and identity provider services.
## Potential solutions
Here is an existing implementation of using this flow to first discover the custom email attribute, and then get it from the JWT payload: https://community.opengroup.org/osdu/platform/system/lib/cloud/aws/os-core-lib-aws/-/blob/master/src/main/java/org/opengroup/osdu/core/aws/entitlements/Authorizer.java#L121https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/10E2E test issue2021-02-23T17:51:46ZRucha DeshpandeE2E test issueDATASET LIST AFTER DELETE
expects the list returned to be of length 6..
The collection posts only datasets and deletes one. In this case, the expected value must be 2.DATASET LIST AFTER DELETE
expects the list returned to be of length 6..
The collection posts only datasets and deletes one. In this case, the expected value must be 2.Rucha DeshpandeRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/12e2e test collection: clean up of collection using gcs urls2021-02-23T17:48:51ZRucha Deshpandee2e test collection: clean up of collection using gcs urlsThere are some requests in the collection that use 'googleapis' url to test.
These need to be cleaned up or changed to env vars.There are some requests in the collection that use 'googleapis' url to test.
These need to be cleaned up or changed to env vars.Rucha DeshpandeDiego MolteniRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/14Validating REGION against hardcoded region names instead of dynamic provider-...2021-02-23T15:31:17ZBrady Spiva [AWS]Validating REGION against hardcoded region names instead of dynamic provider-specific regions## Observed behavior
When attempting to create subprojects, the `storage_location` parameter is restricted to a hardcoded list of values (GCP values?).
These values are hardcoded here, in `services/subproject/parser.ts`:
https://commun...## Observed behavior
When attempting to create subprojects, the `storage_location` parameter is restricted to a hardcoded list of values (GCP values?).
These values are hardcoded here, in `services/subproject/parser.ts`:
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/blob/master/src/services/subproject/parser.ts#L25-31
When attempting to pass an AWS-specific region, this is the error code received:
> [400] [seismic-store-service] The storage_location body field US-EAST-1 is not valid. It must be one of ASIA, EU, US, NORTHAMERICA-NORTHEAST1, US-CENTRAL1, US-EAST1, US-EAST4, US-WEST1, SOUTHAMERICA-EAST1, EUROPE-WEST1, EUROPE-WEST2, EUROPE-WEST3, EUROPE-WEST4, ASIA-EAST1, ASIA-NORTHEAST1, ASIA-SOUTH1, ASIA-SOUTHEAST1, AUSTRALIA-SOUTHEAST1
## Expected behavior
Subproject creation should validate the user-provided region against cloud provider's regions dynamically.
## Potential solutions
This might already be addressed in @DiegoMolteni's upcoming updates to make the Seismic service more abstracted and generic. If not, can we work to abstract `parser.ts` to have cloud provider specific implementations?Rucha DeshpandeDiego MolteniBrady Spiva [AWS]Yunhua KoglinRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/11e2e tests: imptoken collection should be optional for CSPs that do not have i...2021-02-23T04:29:18ZRucha Deshpandee2e tests: imptoken collection should be optional for CSPs that do not have impersonation token implementedimptoken collection should be optional for CSPs that do not have impersonation token implementedimptoken collection should be optional for CSPs that do not have impersonation token implementedRucha DeshpandeDiego MolteniRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/19e2e test: getGCSAccessToken API validates token type2021-02-23T04:26:36ZRucha Deshpandee2e test: getGCSAccessToken API validates token typeThe getGCSAccessToken API test script validates the return token type to be 'Bearer'.
For AWS the return type could be 'STS token'.
This validation should be removedThe getGCSAccessToken API test script validates the return token type to be 'Bearer'.
For AWS the return type could be 'STS token'.
This validation should be removedRucha DeshpandeDiego MolteniRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/20e2e test: Subproject Get New - checks return child length2021-02-23T04:24:39ZRucha Deshpandee2e test: Subproject Get New - checks return child lengthSubproject get new test script validates response child length. It is hardcoded to 8.
The length of the response can vary per CSP.
pm.expect(child.length).to.eql(8);Subproject get new test script validates response child length. It is hardcoded to 8.
The length of the response can vary per CSP.
pm.expect(child.length).to.eql(8);Rucha DeshpandeDiego MolteniRucha Deshpande