You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem description:
I recently needed to configure common settings for the ComposedTaskProperties of the ComposedTaskRunner. However, in the Spring Cloud Dataflow configuration, the only settings available for the ComposedTaskRunner were the ComposedTaskRunnerConfigurationProperties. When setting properties for the CTR using spring.cloud.dataflow.application-properties.task in the Spring Cloud Data Flow server configuration, these properties are injected into all task applications, not just the CTR🥲
Solution description:
It would be great if the dataflow server configuration could be open to allow common settings for the composed task runner. It would be beneficial if OAuth2 settings and timeout configurations could be controlled through common settings.
Additional context:
Is there currently a recommended way to achieve this behavior, or could this feature be considered for a future release?
Thank you for your time and consideration.
The text was updated successfully, but these errors were encountered:
hotjoyit
changed the title
Request for a method to configure ComposedTaskRunner globally without affecting other tasks
Request for a method to configure ComposedTaskRunner globally
Oct 15, 2024
Problem description:
I recently needed to configure common settings for the
ComposedTaskProperties
of the ComposedTaskRunner. However, in the Spring Cloud Dataflow configuration, the only settings available for the ComposedTaskRunner were theComposedTaskRunnerConfigurationProperties
. When setting properties for the CTR usingspring.cloud.dataflow.application-properties.task
in the Spring Cloud Data Flow server configuration, these properties are injected into all task applications, not just the CTR🥲Solution description:
It would be great if the dataflow server configuration could be open to allow common settings for the composed task runner. It would be beneficial if OAuth2 settings and timeout configurations could be controlled through common settings.
Additional context:
Is there currently a recommended way to achieve this behavior, or could this feature be considered for a future release?
Thank you for your time and consideration.
The text was updated successfully, but these errors were encountered: