-
Notifications
You must be signed in to change notification settings - Fork 576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TaskDefinition Detail not returning DSL for CTRs #2763
Comments
cppwfs
pushed a commit
to cppwfs/spring-cloud-dataflow
that referenced
this issue
Jan 31, 2019
cppwfs
pushed a commit
to cppwfs/spring-cloud-dataflow
that referenced
this issue
Jan 31, 2019
markpollack
pushed a commit
that referenced
this issue
Feb 1, 2019
cppwfs
pushed a commit
that referenced
this issue
Feb 1, 2019
resolves #2763 Backport change to support correct name for sanitize
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After investigation it appears that the sanitizeTaskDSL is not correctly cleansing the task DSL for CTR's as shown here:
https://github.com/spring-cloud/spring-cloud-dataflow/blob/master/spring-cloud-dataflow-rest-resource/src/main/java/org/springframework/cloud/dataflow/rest/support/ArgumentSanitizer.java#L161-L165
In this case the TaskDefinition is properly populated but the TaskDefinitionBuilder is not populating the SanitizedTaskDefinition properly. And the TaskDefinitionToDslConverter.toDsl will need to be updated or replaced to handle the CTR Scenario.
Refer to spring-cloud/spring-cloud-dataflow-ui#1026 for additional information.
The text was updated successfully, but these errors were encountered: