(Docker-Compose) Deployed applications should be able to override the datasource configuraitons inherided from the Skipper or Dataflow servers #4359
Assignees
Labels
type/bug
Is a bug report
Comments
tzolov
added a commit
to tzolov/spring-cloud-dataflow
that referenced
this issue
Feb 1, 2021
- In the docker-compose configuration, replace the datasource env. variables (e.g. like SPRING_DATASOURCE_URL) by Spring properties to allow the apps to override it. Resolves spring-cloud#4359
|
Issue moved to spring-cloud/spring-cloud-deployer-local #202 via ZenHub |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, for the local deployment, the Spring datasource configuration of thg Dataflow/Skipper server is passed to the deployed applications as part of the environment context.
This affects only the maven/jar applications deployed in local mode.
Because the existing docker-compose configurations uses env. variables (e.g.
SPRING_DATASOURCE_URL) instead of properties (like--spring.datasource.url) the deployed streaming apps are not able to configure customer per-app datasources.The text was updated successfully, but these errors were encountered: