SonataflowPlatform persistence change apply the workflow, DI and JS restarts, but the JS don't restart well

[wmedvede]

Describe the bug

1) We create a SPF with persistence configured, and DI and JS enabled that use that platform persistence. 2) We deploy a workflow in that platform and let it use that platform persistence. 3) DI, JS and the workflow starts well, etc.

4) now we change the original SPF persistence configuration to point to another DB.

5) DI is restarted and points to the new DB 6) workflow is restarted and points to the new DB

7) Jobs service is restarted but we have the following situation:

7.1) The deployment has the QUARKUS_DATASOURCE_JDBC_URL pointing to the new DB 7.2) The sonataflow-platform-jobs-service-props ConfigMap, still has the quarkus.datasource.reactive.url pointing to the old DB. (It looks like the sonataflow-platform-jobs-service-props ConfigMap is not refreshed as part of the SPF change)

So the restart don't well, since same instance points to two different databases.

Expected behavior

All jobs service connections must point to the new DB.

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

[ricardozanini]

@wmedvede can we close this one?

[wmedvede]

@ricardozanini I need to double check, will add on my list