Wellbore-cloud issueshttps://community.opengroup.org/groups/osdu/platform/domain-data-mgmt-services/wellbore/lib/wellbore-cloud/-/issues2023-12-21T12:07:01Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/lib/wellbore-cloud/wellbore-gcp-lib/-/issues/2Add trigger trusted to the CICD2023-12-21T12:07:01ZYan Sushchynski (EPAM)Add trigger trusted to the CICDhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/lib/wellbore-cloud/wellbore-gcp-lib/-/issues/1Add multipartition support2023-09-13T10:24:24ZYan Sushchynski (EPAM)Add multipartition supportThere is no multipartition support for the `GC` implementation. It causes a few problems:
1. We are forced to specify a GC project id
2. We have to use default bucket names
3. We can't separate the data in different partitionsThere is no multipartition support for the `GC` implementation. It causes a few problems:
1. We are forced to specify a GC project id
2. We have to use default bucket names
3. We can't separate the data in different partitionshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/lib/wellbore-cloud/wellbore-azure-lib/-/issues/1Add retry/timeout mechanism around AzureDefaultCredential2023-03-21T15:05:19ZYannickAdd retry/timeout mechanism around AzureDefaultCredentialIn some deployments, upon load traffic, AzureDefaultCredential fails to properly get credentials. Then add some retry and timeout to be more resilient regarding these failure.In some deployments, upon load traffic, AzureDefaultCredential fails to properly get credentials. Then add some retry and timeout to be more resilient regarding these failure.Cyril MonmoutonCyril Monmoutonhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/lib/wellbore-cloud/wellbore-aws-lib/-/issues/1`osdu_api` incompatibilities between wellbore-aws-lib and wellbore-anthos-lib2022-12-15T14:20:59ZYan Sushchynski (EPAM)`osdu_api` incompatibilities between wellbore-aws-lib and wellbore-anthos-libHello!
We are going to introduce Anthos provider in Wellbore DMS in 0.15 release.
We added some code to `osdu_api` in order to work with Anthos: https://community.opengroup.org/osdu/platform/system/sdks/common-python-sdk/-/tree/master...Hello!
We are going to introduce Anthos provider in Wellbore DMS in 0.15 release.
We added some code to `osdu_api` in order to work with Anthos: https://community.opengroup.org/osdu/platform/system/sdks/common-python-sdk/-/tree/master/osdu_api/providers/anthos.
And we refer to those `osdu_api` changes in our `wellbore-anthos-lib`: https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/lib/wellbore-cloud/wellbore-anthos-lib/-/blob/master/setup.py#L10.
The problem appears when we try to `pip-compile requirements.in` file in `Wellbore DMS`:
```
There are incompatible versions in the resolved dependencies:
osdu-api~=0.15.0.dev (from osdu-core-lib-python-anthos==1.0.1->-r requirements.in (line 44))
osdu-api==0.14.0 (from osdu-core-lib-python-aws==1.0.1->-r requirements.in (line 43))
```
I can see two possible solutions in this case:
1. Keep the same `osdu_api` version in `wellbore-anthos-lib` and `wellbore-aws-lib`;
1. Decouple `pip-compile` in `Wellbore DMS` for different cloud providersYifei XuOkoun-Ola Fabien HouetoTravis PurcellSean FisherYifei Xu