-
Notifications
You must be signed in to change notification settings - Fork 1.8k
fix(flows): avoid failing flow dependencies with dynamic defaults #11166
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
fix(flows): avoid failing flow dependencies with dynamic defaults #11166
Conversation
f1c9d8a
to
c25cda3
Compare
🐋 Docker image: docker run --pull=always --rm -it -p 8080:8080 --user=root -v /var/run/docker.sock:/var/run/docker.sock -v /tmp:/tmp ghcr.io/kestra-io/kestra-pr:11166 server local |
1 similar comment
🐋 Docker image: docker run --pull=always --rm -it -p 8080:8080 --user=root -v /var/run/docker.sock:/var/run/docker.sock -v /tmp:/tmp ghcr.io/kestra-io/kestra-pr:11166 server local |
c25cda3
to
e9bae98
Compare
🐋 Docker image: docker run --pull=always --rm -it -p 8080:8080 --user=root -v /var/run/docker.sock:/var/run/docker.sock -v /tmp:/tmp ghcr.io/kestra-io/kestra-pr:11166 server local |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I understand it, you said that it's normal to not be able to resolve inputs?
This is unfortunate as it would means that we would allow nonn-working flow to be defined...
e9bae98
to
e596479
Compare
🐋 Docker image: docker run --pull=always --rm -it -p 8080:8080 --user=root -v /var/run/docker.sock:/var/run/docker.sock -v /tmp:/tmp ghcr.io/kestra-io/kestra-pr:11166 server local |
closes #11117
The main issue is that input defaults are trying to get resolved but if themselves depend on another inputs it's getting painful.
A better way may be to do the same as for resolve input endpoint or resolve other input defaults while keeping track of failed input resolutions and create a new renderer with the resolved input values and keep iterating till the failure list is no longer reducing or empty but it feels overkill and I don't think handling this case is useful as it's failing only in a "static" context (flow dependencies computing)