wmedvede opened a new issue, #476:
URL: 
https://github.com/apache/incubator-kie-kogito-serverless-operator/issues/476

   ### Describe the bug
   
   Given a configuration like below, we have that data-index and jobs-service 
must inherit the persistence configuration from the platform. However if we set 
for example persitence: {} for the jobs service, we get an segmentation error 
at deploytime.
   
   
   ```
   apiVersion: sonataflow.org/v1alpha08
   kind: SonataFlowPlatform
   metadata:
     name: sonataflow-platform
   spec:
     services:
       # no persistence is defined for the DI, it will take it from the SFP if 
any.
       dataIndex:
         enabled: true
       jobService:
         # no persistence is defined for the JS, it will take it from the SFP 
if any.
         enabled: true
         persistence: {}
     persistence:
       postgresql:
         secretRef:
           name: postgres-secrets
           userKey: POSTGRESQL_USER
           passwordKey: POSTGRESQL_PASSWORD
         serviceRef:
           name: postgres
           databaseName: sonataflow
   ```
   
   
   
   ### Expected behavior
   
   The deployment of both services must work an take the persistence 
configuration from the platform.
   
   ### Actual behavior
   
   _No response_
   
   ### How to Reproduce?
   
   _No response_
   
   ### Output of `uname -a` or `ver`
   
   _No response_
   
   ### Golang version
   
   _No response_
   
   ### Operator-sdk version
   
   _No response_
   
   ### SonataFlow Operator version or git rev
   
   _No response_
   
   ### Additional information
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to