seismic-dms-service issueshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues2021-02-23T04:27:47Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/15502 Gateway Error on calling Redis get and set functions2021-02-23T04:27:47ZWalter D502 Gateway Error on calling Redis get and set functionsHi @DiegoMolteni
We have been getting the 502 Gateway Error for some APIs. One of the APIs is Create Subproject API. On debugging the code the error is thrown on the following 2 lines in compliance.ts file in the create subproject flow:...Hi @DiegoMolteni
We have been getting the 502 Gateway Error for some APIs. One of the APIs is Create Subproject API. On debugging the code the error is thrown on the following 2 lines in compliance.ts file in the create subproject flow:
1. await this._cache.set(ltag, results.invalidLegalTags.length === 0);
2. await this._cache.set(ltag, results.invalidLegalTags.length === 0);
Interestingly, this is happening on the DEV environment. I've not encountered the issue in my local. Have you faced this error or have a clue on what the problem could be? Any help would be appreciated. Thank you.M1 - Release 0.1Diego MolteniDaniel PerezDiego Molteni2021-02-26https://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 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/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/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/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/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/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