wmedvede opened a new issue, #408:
URL:
https://github.com/apache/incubator-kie-kogito-serverless-operator/issues/408
### Describe the bug
When we configure the persistence for a workflow like below, and we don't
set any databaseSchema name, the operator is creating a jdbc url like this:
jdbc:postgresql://postgres.usecase3-persistence:5432/sonataflow?currentSchema=default
A schema with name 'default' is configured, however this schema don't
exists. Instead, by default postgresql has a schema with the name 'public'.
So, for that case, we should:
1. Set no schema at all, create the url like this:
jdbc:postgresql://postgres.usecase3-persistence:5432/sonataflow and the
'public' schema should be automatically picked up.
2. Simply use 'public' instead of 'default'
3. Use the workflow name as the schema name. (This last option I believe it
was already discussed during development and discarded)
```
spec:
persistence:
postgresql:
secretRef:
name: postgres-secrets
userKey: POSTGRES_USER
passwordKey: POSTGRES_PASSWORD
serviceRef:
name: postgres
databaseName: sonataflow
```
### Expected behavior
_No response_
### Actual behavior
Right now, when we create a workflow instance an error is produced since the
queries are executed against the configured 'default' schema that don't exists.
### 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]
