GC Infrastructure code issueshttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues2023-05-29T09:00:39Zhttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues/22OSDU Provisioning Has Pods Perpetually In CrashLoopBackoff2023-05-29T09:00:39ZAndrew HeadOSDU Provisioning Has Pods Perpetually In CrashLoopBackoffI am trying to set up a developer instance of the OSDU to investigate how we would go about using it within my organisation. After several attempts at provisioning various different Helm charts following instructions on the OSDU git our...I am trying to set up a developer instance of the OSDU to investigate how we would go about using it within my organisation. After several attempts at provisioning various different Helm charts following instructions on the OSDU git our team managed to get an instance running using docker desktop, however it seems very prone to falling over with some pods never getting out of a CrashLoopBackOff cycle. Below is the instructions we have developed for getting as far as we have:
[OSDU_Dev_Setup.docx](/uploads/bd06dfcdecff4a286d1aa1de7aa0dcdf/OSDU_Dev_Setup.docx)
Subsequently I have commissioned a VM with 64GB of memory (and allocated 50GB to the WSL) in case a lack of resources on the 32GB version referenced in the instructions was causing the issue, however the same problems seem to be presenting themselves.Dzmitry Malkevich (EPAM)Dzmitry Malkevich (EPAM)https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues/19On-Prem OSDU release/0.18 legal-bootstrap is failing2023-02-10T14:30:35ZFabien BosquetOn-Prem OSDU release/0.18 legal-bootstrap is failingI have noticed when deploying osdu-onprem using docker-desktop that the legal-bootstrap-deployment is failing.
![image](/uploads/b069d8fce03b24b7083edb1e4a9a397d/image.png)
![image](/uploads/7f4ebb0c57ecb50648eadeebd5284443/image.png)
...I have noticed when deploying osdu-onprem using docker-desktop that the legal-bootstrap-deployment is failing.
![image](/uploads/b069d8fce03b24b7083edb1e4a9a397d/image.png)
![image](/uploads/7f4ebb0c57ecb50648eadeebd5284443/image.png)
The issue occurs when deploying osdu-onprem from branch `release/0.18`
```
cd infra-gcp-provisioning/examples/simple_osdu_onprem
helm install -f custom-values.yaml -f custom-release.yaml osdu-onprem ../../helm/osdu-infra-onprem/
```
The logs shows that the issue is with the two `Bearer` in the authorization header in the `create legal tag` step.
```
+ echo 'Trying to create legal tag for initial data bootstrap'
+ cat
++ curl --location -g --request POST --url http://legal/api/legal/v1/legaltags --write-out '%{http_code}' --silent --output output.txt --header 'Content-Type: application/json' --header 'authorization: Bearer Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJrajN5VmFkTEpYRk5IRzFEcWd4dnNXNVB5U04tT3FvRjBSYUkxOEt2MDE0In0.eyJleHAiOjE2NzUyNTg5NDMsImlhdCI6MTY3NTI1NTM0MywiYXV0aF90aW1lIjowLCJqdGkiOiI4ODg5Zjc2MC0wYjAxLTQwMjQtODU3MS03YmI5NDYwYmU0NzkiLCJpc3MiOiJodHRwOi8va2V5Y2xvYWsvcmVhbG1zL29zZHUiLCJhdWQiOiJkYXRhZmllciIsInN1YiI6Ijg1NDhlZjVhLWNkNDEtNDlmMy05Y2IzLTcyOWVhMmM5MmIyMyIsInR5cCI6IklEIiwiYXpwIjoiZGF0YWZpZXIiLCJhdF9oYXNoIjoiandOYWRNUkRZNUhrMHpZQnZSeDE5ZyIsImFjciI6IjEiLCJjbGllbnRIb3N0IjoiMTI3LjAuMC42IiwiY2xpZW50SWQiOiJkYXRhZmllciIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwicHJlZmVycmVkX3VzZXJuYW1lIjoic2VydmljZS1hY2NvdW50LWRhdGFmaWVyIiwiY2xpZW50QWRkcmVzcyI6IjEyNy4wLjAuNiIsImVtYWlsIjoiZGF0YWZpZXJAc2VydmljZS5sb2NhbCJ9.cKhGwHMYHFITSSLRpcK4Iwvr72vMrLtD1hZ1Y0jAmRJSswlaw4VpRJEpBXDsBAVBR9StC5a0-AX8cFNSvpAnh570CzKulazIxCrmknh8sm_Dnjjs9Ho4CscE3DyVMIupQ4UBLzaSjp9SxGKGAI_3OnpJSBIKb7kG0faPXZgjlAOzW44VLAGsYi0UdEClTfWyaFdtfU7ukieG1ILJO1ENBgrS0KuuWtt6EfZXIPCTuRLdF3uu-NkKp03FA1XVh7Xzb49tZOHSJVoV-hE9VMnbO3t_cdG53lDH-jvR50f8S_-vNOvlPh_6u6Klz_o-_eqYP5cEowMX5p7qFs0bzjuccQ' --header 'data-partition-id: osdu' --data @/opt/default_legal_tag.json
+ status_code=401
+ '[' 401 == 201 ']'
+ '[' 401 == 409 ']'
+ cat /opt/output.txt
+ exit 1
{"code":401,"reason":"Access denied","message":"The user is not authorized to perform this action"}
```
It looks to me that the issue was already fixed in the master branch of the legal project:
https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/340
My request is :
- cherry pick that [merge request](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/merge_requests/340) to the `release/0.18` branch of the `legal` project
- update the https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/blob/v0.18.0/examples/simple_osdu_onprem/custom-release.yaml to use a new `gcp_legal_deploy.bootstrapImage`https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues/14OSDU simple on prem - Installation failed2022-08-24T21:17:51ZChad LeongOSDU simple on prem - Installation failedTrying to follow the guide here: https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/tree/master/examples/simple_osdu_onprem
When I run this : `helm install -f custom-values.yaml osdu-anthos ...Trying to follow the guide here: https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/tree/master/examples/simple_osdu_onprem
When I run this : `helm install -f custom-values.yaml osdu-anthos ../../helm/osdu-infra-onprem/`
I get the following error:
`Error: INSTALLATION FAILED: Kubernetes cluster unreachable: Get "https://172.24.102.107:8443/version": dial tcp 172.24.102.107:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.`Dzmitry Malkevich (EPAM)Dzmitry Malkevich (EPAM)https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues/13On-prem deployment - Development Mode - Helm issues2022-06-23T15:59:19ZJane McConnellOn-prem deployment - Development Mode - Helm issuesDzmitry Malkevich (EPAM)Dzmitry Malkevich (EPAM)https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues/10On Prem Deployment failing after getting latest code from master branch2022-05-24T18:37:35ZMatt WiseOn Prem Deployment failing after getting latest code from master branchThe following error is observed after pulling latest code, running `helm dependency update`, then trying to install via `helm install osdu-onprem .`
```bash
Error: INSTALLATION FAILED: template: osdu-gcp-onprem/charts/gcp_partition_con...The following error is observed after pulling latest code, running `helm dependency update`, then trying to install via `helm install osdu-onprem .`
```bash
Error: INSTALLATION FAILED: template: osdu-gcp-onprem/charts/gcp_partition_configmap/templates/partition-bootstrap-configmap.yml:13:98: executing "osdu-gcp-onprem/charts/gcp_partition_configmap/templates/partition-bootstrap-configmap.yml" at <"istio-ingressgateway">: nil pointer evaluating interface {}.loadBalancer
```JoeKateryna Kurach (EPAM)Matt WiseDzmitry Malkevich (EPAM)Joehttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues/9On-Prem Deployment - Storage Service Issues2022-05-24T18:36:32ZMatt WiseOn-Prem Deployment - Storage Service Issues# Storage Issues
* All calls to storage service fail with the following returned error message and log
request response:
```bash
upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport fa...# Storage Issues
* All calls to storage service fail with the following returned error message and log
request response:
```bash
upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: delayed connect error: 111
```
log:
```bash
{"timestamp":"2022-05-11 19:10:29.444","thread":"main","logger":"org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener","message":"\n\nError starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.","context":"default","severity":"INFO"}
{"timestamp":"2022-05-11 19:10:29.600","thread":"main","logger":"org.springframework.boot.SpringApplication","message":"Application run failed","context":"default","exception":"org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tenantFactory' defined in URL [jar:file:/app/storage-gcp.jar!/BOOT-INF/lib/core-lib-gcp-0.14.0-rc2.jar!/org/opengroup/osdu/core/gcp/multitenancy/TenantFactory.class]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.opengroup.osdu.core.gcp.multitenancy.TenantFactory]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: A project ID is required for this service but could not be determined from the builder or the environment. Please set a project ID using the builder.\n\tat org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1334)\n\tat org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1232)\n\tat org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:582)\n\tat org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542)\n\tat org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)\n\tat org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)\n\tat org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)\n\tat org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)\n\tat org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:944)\n\tat org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918)\n\tat org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583)\n\tat org.springframework.boot.SpringApplication.refresh(SpringApplication.java:754)\n\tat org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:434)\n\tat org.springframework.boot.SpringApplication.run(SpringApplication.java:338)\n\tat org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:143)\n\tat org.springframework.boot.builder.SpringApplicationBuilder.runAndExtractParent(SpringApplicationBuilder.java:227)\n\tat org.springframework.boot.builder.SpringApplicationBuilder.sibling(SpringApplicationBuilder.java:258)\n\tat org.opengroup.osdu.storage.provider.gcp.StorageApplicationGCP.main(StorageApplicationGCP.java:37)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\tat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat java.lang.reflect.Method.invoke(Method.java:498)\n\tat org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)\n\tat org.springframework.boot.loader.Launcher.launch(Launcher.java:108)\n\tat org.springframework.boot.loader.Launcher.launch(Launcher.java:58)\n\tat org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)\nCaused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.opengroup.osdu.core.gcp.multitenancy.TenantFactory]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: A project ID is required for this service but could not be determined from the builder or the environment. Please set a project ID using the builder.\n\tat org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:224)\n\tat org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:87)\n\tat org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1326)\n\t... 25 common frames omitted\nCaused by: java.lang.IllegalArgumentException: A project ID is required for this service but could not be determined from the builder or the environment. Please set a project ID using the builder.\n\tat com.google.common.base.Preconditions.checkArgument(Preconditions.java:145)\n\tat com.google.cloud.ServiceOptions.<init>(ServiceOptions.java:304)\n\tat com.google.cloud.datastore.DatastoreOptions.<init>(DatastoreOptions.java:97)\n\tat com.google.cloud.datastore.DatastoreOptions.<init>(DatastoreOptions.java:35)\n\tat com.google.cloud.datastore.DatastoreOptions$Builder.build(DatastoreOptions.java:86)\n\tat org.opengroup.osdu.core.gcp.multitenancy.DatastoreCreator.get(TenantInfoDatastoreRepo.java:90)\n\tat org.opengroup.osdu.core.gcp.multitenancy.TenantInfoDatastoreRepo.<init>(TenantInfoDatastoreRepo.java:46)\n\tat org.opengroup.osdu.core.gcp.multitenancy.TenantFactory.<init>(TenantFactory.java:37)\n\tat sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)\n\tat sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)\n\tat sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)\n\tat java.lang.reflect.Constructor.newInstance(Constructor.java:423)\n\tat org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:211)\n\t... 27 common frames omitted\n","severity":"ERROR"}
```JoeKateryna Kurach (EPAM)Matt WiseJoehttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues/7On-Prem Deployment - Legal Service Issues2022-05-24T18:41:03ZMatt WiseOn-Prem Deployment - Legal Service Issues#Legal Service Issues
* When calling legal service, no return body is received and the request is stuck until manually cancelled or times out.
* Service shows '307' (Redirect) on every request for status. Example log:
```json
{"timesta...#Legal Service Issues
* When calling legal service, no return body is received and the request is stuck until manually cancelled or times out.
* Service shows '307' (Redirect) on every request for status. Example log:
```json
{"timestamp":"2022-05-11 21:17:28.932","thread":"http-nio-8080-exec-8","mdc":{"user":"entitlements_admin@service.local","correlation-id":"1c2feb19-f873-4870-8275-e2d02d22fec8","data-partition-id":"osdu"},"logger":"org.opengroup.osdu.core.common.logging.DefaultLogWriter","message":"#RequestLog Request(requestMethod=GET, latency=PT0.001S, requestUrl=http://[redacted]/api/legal/v1/legaltags, Status=307, ip=192.168.5.20) {correlation-id=1c2feb19-f873-4870-8275-e2d02d22fec8, data-partition-id=osdu}","context":"default","severity":"INFO"}
```JoeKateryna Kurach (EPAM)Matt WiseJoehttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues/6On-Prem Deployment - Entitlements/Auth Issues2022-05-24T18:40:34ZMatt WiseOn-Prem Deployment - Entitlements/Auth Issues
# Entitlements Issues
* Initial keycloak admin user does not have OSDU entitlements. Therefore cannot give new users permission in OSDU groups.
* Had to go into keycloak and add a new user that impersonated the 'entitlements_admin@s...
# Entitlements Issues
* Initial keycloak admin user does not have OSDU entitlements. Therefore cannot give new users permission in OSDU groups.
* Had to go into keycloak and add a new user that impersonated the 'entitlements_admin@service.local' service account and allowed password auth to be able to connect to the system and run entitlements groups commands.
* Access token does not expire (tested after 3 days of non-use)
* JWT Parsed on jwt.io shows the token should expire on Wed, May 11th...but still works as of Mon, May 16th.
```json
{
"exp": 1652307430, //Wednesday, May 11, 2022 10:17:10 PM
"iat": 1652303830,
"jti": "3d0ef4cf-da19-401f-b107-1dc6a8d6fbd5",
"iss": "http://[redacted]/auth/realms/osdu",
"aud": "account",
"sub": "0125808f-3935-4dbf-9167-980a4e90b4cd",
"typ": "Bearer",
"azp": "storage",
"session_state": "2c5fe593-6882-43ed-a4d9-c4adc0021f8d",
"acr": "1",
"realm_access": {
"roles": [
"offline_access",
"default-roles-osdu",
"uma_authorization"
]
},
"resource_access": {
"account": {
"roles": [
"manage-account",
"manage-account-links",
"view-profile"
]
}
},
"scope": "email profile",
"sid": "2c5fe593-6882-43ed-a4d9-c4adc0021f8d",
"email_verified": true,
"preferred_username": "[redacted]",
"email": "[redacted]"
}
```JoeKateryna Kurach (EPAM)Matt WiseJoehttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues/5On-Prem Deployment - Helm Deployment Issues2022-05-24T18:38:02ZMatt WiseOn-Prem Deployment - Helm Deployment Issues# Deploy Issues
* Duplicate env var params in values.yaml trigger warning on helm install. I'm not sure which vars are actually being used
```bash
W0516 10:21:48.347382 5478 warnings.go:70] spec.template.spec.containers[0].env[20]....# Deploy Issues
* Duplicate env var params in values.yaml trigger warning on helm install. I'm not sure which vars are actually being used
```bash
W0516 10:21:48.347382 5478 warnings.go:70] spec.template.spec.containers[0].env[20].name: duplicate name "AIRFLOW_DATABASE_HOST"
W0516 10:21:48.347428 5478 warnings.go:70] spec.template.spec.containers[0].env[21].name: duplicate name "AIRFLOW_DATABASE_PORT_NUMBER"
W0516 10:21:48.347441 5478 warnings.go:70] spec.template.spec.containers[0].env[22].name: duplicate name "AIRFLOW_DATABASE_NAME"
W0516 10:21:48.347453 5478 warnings.go:70] spec.template.spec.containers[0].env[23].name: duplicate name "AIRFLOW_DATABASE_USERNAME"
W0516 10:21:48.347463 5478 warnings.go:70] spec.template.spec.containers[0].env[24].name: duplicate name "AIRFLOW_DATABASE_PASSWORD"
W0516 10:21:48.639137 5478 warnings.go:70] spec.template.spec.containers[0].env[24].name: duplicate name "AIRFLOW_DATABASE_HOST"
W0516 10:21:48.639183 5478 warnings.go:70] spec.template.spec.containers[0].env[25].name: duplicate name "AIRFLOW_DATABASE_PORT_NUMBER"
W0516 10:21:48.639194 5478 warnings.go:70] spec.template.spec.containers[0].env[26].name: duplicate name "AIRFLOW_DATABASE_NAME"
W0516 10:21:48.639204 5478 warnings.go:70] spec.template.spec.containers[0].env[27].name: duplicate name "AIRFLOW_DATABASE_USERNAME"
W0516 10:21:48.639213 5478 warnings.go:70] spec.template.spec.containers[0].env[28].name: duplicate name "AIRFLOW_DATABASE_PASSWORD"
```JoeKateryna Kurach (EPAM)Matt WiseJoehttps://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues/4First deployment experience2021-10-18T18:56:31ZCoen SmitsFirst deployment experienceI've been trying to get OSDU deployed on GCP using these scripts. The goal is to have a deployment to play around with for my developer group.
The first mistake I made was using what was in the master branch. That was probably not right...I've been trying to get OSDU deployed on GCP using these scripts. The goal is to have a deployment to play around with for my developer group.
The first mistake I made was using what was in the master branch. That was probably not right, but I got it to deploy most of the services. **It would be a nice addition if the readme would have a block with which branch to get.**
Now.. I did switch to the release/0.11 branch, since I *think* that is the right branch. Just like the master branch, it went all the way through Terraform. But I believe I am missing some DAGs, since all I get is the airflow_monitoring DAG, and was expecting the Osdu_ingest DAG.
The reason why I am expecting that DAG is because I am trying to generate some test data using this: https://community.opengroup.org/osdu/platform/data-flow/data-loading/open-test-data/-/tree/release/0.11
I'd suggest that **having a link to the test data would be a nice addition to the end of the readme** as well.
So my status now: Terraform went through, all services seem to be installed (unit service has a lot of units in it, so I got the OAuth part working).
But the main question: **Am I correct that I should have the Osdu_ingest DAG after running through these scripts?**Yan Sushchynski (EPAM)Yan Sushchynski (EPAM)https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues/3Deployment framework [H1] [GONRG-619]2021-07-07T13:41:23ZSergey Krupenin (EPAM)Deployment framework [H1] [GONRG-619]https://jiraeu.epam.com/browse/GONRG-619https://jiraeu.epam.com/browse/GONRG-619M7 - Release 0.10Oleksandr Kosse (EPAM)Oleksandr Kosse (EPAM)https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues/2Readme update suggestions2023-07-13T20:08:07ZChad BrockmanReadme update suggestionsI've got a few suggestions I think would improve the readme.md
---
The about section references an out of date github repo -- the reference should be removed.
https://community.opengroup.org/osdu/platform/deployment-and-operations/infr...I've got a few suggestions I think would improve the readme.md
---
The about section references an out of date github repo -- the reference should be removed.
https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning#about
---
In Prerequisites -- #6 about Elastic
https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning#prerequisites
I think it needs to be explained in a clearer manner -- i.e. outline the options and when they’re appropriate:
Production:
-Marketplace
-ECE (why is it preferred?)
-GKE HELM
Dev:
-Elasticsearch on GCE
---
In Prerequisites -- #6 about Elastic
The instructions for "Elasticsearch on GCE" reference a folder and script that don't exist. I think it's a good option - could we fix the instructions?
---
In the Preparation section
https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning#preparation
It would be nice if there was a simple diagram explaining the project layout options - i.e. all in one project or services / data separate projects.
It would also be nice if the "operator" user creation had a combined option when running services and data in the same project.
---
In the environment variables section - it might be nice to add a line that says "detailed explanations below table" pointer? (or I was just too distracted to notice on my 1st run through...)
---
Thanks! ChadOleksii Tsyganov (EPAM)Oleksii Tsyganov (EPAM)https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioning/-/issues/1Publish infra-gcp-provisioning repository [GCP]2020-06-26T11:34:49ZElizaveta Zeldina (EPAM)Publish infra-gcp-provisioning repository [GCP]Publish infra-gcp-provisioning repository to https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioningPublish infra-gcp-provisioning repository to https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-gcp-provisioningDmitriy RudkoDmitriy Rudko