jordigilh commented on issue #379:
URL: 
https://github.com/apache/incubator-kie-kogito-serverless-operator/issues/379#issuecomment-1919495823

   > @jordigilh The workflow is like this, so should default to Prod.
   > 
   > apiVersion: sonataflow.org/v1alpha08 kind: SonataFlow metadata: name: 
callbackstatetimeouts annotations: sonataflow.org/description: Callback State 
Timeouts Example k8s sonataflow.org/version: 0.0.1 spec: flow: start: 
PrintStartMessage events:
   
   Weird. Yes it should default to a production profile if none is specified. I 
use [this 
one](https://github.com/apache/incubator-kie-kogito-serverless-operator/blob/main/test/testdata/platform/services/prod/postgreSQL/sonataflow/04-sonataflow_callbackstatetimeouts.sw.yaml)
 and it fails to start because it's missing the jdbc connection url:
   ```
   apiVersion: sonataflow.org/v1alpha08
   kind: SonataFlow
   metadata:
     name: callbackstatetimeouts
     annotations:
       sonataflow.org/description: Callback State Timeouts Example k8s
       sonataflow.org/version: 0.0.1
       sonataflow.org/profile: prod
   ```
   
   The strange thing is that it was not failing before and I don't think the 
code that handles this has changed recently.
   
   So you're saying that this WF now requires persistence, either it uses 
ephemeral if none provided or it will use an existing service otherwise. I'm 
fine if that's the case, but I need a WF that does not have such requirement 
for the platform testing. Is there any WF in the tech demo repository that can 
be used to validate along with DI and JS?


-- 
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