-
Notifications
You must be signed in to change notification settings - Fork 579
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
Streams retain properties after a failed deployment and cannot be overwritten without destroying and recreating. #5814
Comments
@cribble-uwindsor In my testing the spring.datasource properties are updated with the values passed and provided to pod as arguments. |
Closing due to inactivity. If closed in error please let us know. |
Hi, please re-open. I'm sorry, I totally missed @corneil comment earlier. The property |
@cribble-uwindsor What do you expect the stream to do when a pod doesn't deploy correctly? How long should we wait before deciding to destroy the stream? |
My expectation would be that the stream could be undeployed and then configuration changed and re-deployed. After that, the pod and stream should deploy fine. In our case, we're seeing the original bad config "stick" despite correcting it after the failure. Would it help if I made a video or some screenshots of replicating the issue? |
Description:
This is similar to #5375 but not exactly like it. They may be related though.
If I create a stream and one or more of my stream components does not deploy properly, the properties from that deploy become "stuck" and I cannot update or clear them without doing a full destroy of the stream and recreating it.
Release versions:
Data Flow Server Implementation
Name: spring-cloud-dataflow-server
Version: 2.11.2-SNAPSHOT
Commit: 86b53e0
Steps to reproduce:
jdbc | log
stream via the UI (This could be any stream definition really that you can cause to error)The text was updated successfully, but these errors were encountered: