seismic-dms-service issueshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues2023-09-19T14:01:16Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/110v3 to v4 sync design2023-09-19T14:01:16ZMark Yanv3 to v4 sync designDiego MolteniDiego Moltenihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/88Generate OpenAPI from the code2023-07-12T13:48:47ZSacha BrantsGenerate OpenAPI from the codeNova LaderNova Laderhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/85osdu:wks:master-data--Seismic3DInterpretationSet:1.1.02023-06-13T19:54:33ZSacha Brantsosdu:wks:master-data--Seismic3DInterpretationSet:1.1.0https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/84osdu:wks:master-data--Seismic2DInterpretationSet:1.1.02023-06-13T19:52:58ZSacha Brantsosdu:wks:master-data--Seismic2DInterpretationSet:1.1.0https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/83osdu:wks:work-product-component--SeismicHorizon:1.1.02023-06-13T19:53:40ZSacha Brantsosdu:wks:work-product-component--SeismicHorizon:1.1.0Nova LaderNova Laderhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/82osdu:wks:work-product-component--NotionalSeismicLine:1.0.02023-07-12T13:48:38ZSacha Brantsosdu:wks:work-product-component--NotionalSeismicLine:1.0.0Nova LaderNova Laderhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/81osdu:wks:master-data--Seismic3DInterpretationSet:1.1.02023-06-06T18:39:50ZSacha Brantsosdu:wks:master-data--Seismic3DInterpretationSet:1.1.0Rashaad GrayRashaad Grayhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/80osdu:wks:master-data--Seismic2DInterpretationSet:1.1.02023-06-06T18:39:25ZSacha Brantsosdu:wks:master-data--Seismic2DInterpretationSet:1.1.0Rashaad GrayRashaad Grayhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/60PATCH API endpoint on subproject. Where can one find the list or guiding docu...2022-07-05T11:54:13ZKamlesh TodaiPATCH API endpoint on subproject. Where can one find the list or guiding document that helps determine as to what can be patched and what cannot be patched.PATCH API endpoint on subproject. Where can one find the list or guiding document that helps determine as to what can be patched and what cannot be patched. Because when I am trying to execute
curl --location --request PATCH 'https://os...PATCH API endpoint on subproject. Where can one find the list or guiding document that helps determine as to what can be patched and what cannot be patched. Because when I am trying to execute
curl --location --request PATCH 'https://osdu-cpd-osdu.osdu-og-platform-validati-ba8e38d4c011d627379af1a4280c4e35-0000.sjc03.containers.appdomain.cloud/osdu-seismic/api/v3/subproject/tenant/opendes/subproject/autotest?recursive=false' \
--header 'Content-Type: application/json' \
--header 'data-partition-id: opendes' \
--header 'ltag: opendes-SeismicDMS-Legal-Tag-Test2951201' \
--header 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5c...B2FJ2Oqvw' \
--data-raw '{
"access_policy": "dataset",
"acls": {
"admins": [
"data.sdms.opendes.autotest.783673ca-3095-4900-ab02-fafe9bb5246f.admin@opendes.ibm.com"
],
"viewers": [
"data.sdms.opendes.autotest.783673ca-3095-4900-ab02-fafe9bb5246f.viewer@opendes.ibm.com"
]
}
}'
I get the message/response 400 Bad Request
[seismic-store-service] The subproject access policy cannot be patched.https://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/41Add new version info endpoint2023-06-13T20:06:33ZSiarhei Khaletski (EPAM)Add new version info endpointOriginal ADR: https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/issues/47
Additional info: https://community.opengroup.org/osdu/platform/home/-/issues/36Original ADR: https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/issues/47
Additional info: https://community.opengroup.org/osdu/platform/home/-/issues/36https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/38Enable forwarding of original request headers to Dataecosystem APIs2021-11-18T13:21:05ZRucha DeshpandeEnable forwarding of original request headers to Dataecosystem APIsIn the current implementation, wherever Dataecosystem APIS are called, headers are re-created. This does not allow any headers from original request - 'x-user-id' for example from being forwarded.
![image](/uploads/d41f01c1648b16625ded5...In the current implementation, wherever Dataecosystem APIS are called, headers are re-created. This does not allow any headers from original request - 'x-user-id' for example from being forwarded.
![image](/uploads/d41f01c1648b16625ded5b18f13d9363/image.png)
Core code has to be modified to 'append' to original headers if there are any new headers, else re-use original request headers.Rucha DeshpandeDiego MolteniGregYunhua 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/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/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/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/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/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 Deshpande