-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
custom waiters with dynamic values, applied to appflow #29911
Conversation
9cde188
to
676f022
Compare
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.
Nice clean implementation 👍
"expected": "blah", | ||
"matcher": "path", | ||
"state": "success", | ||
"argument": "{{not a valid jinja template 💀}}" |
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.
LOLOLOL 💀 ❤️
f"Parameter was not supplied for templated waiter's acceptor '{arg}'", e | ||
) | ||
return config | ||
|
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.
Yeah. I think I like this solution. I could nitpick the variable names but I always do that. :P
@vincbeck and @Taragolis are you happy with the changes in response to your comments? |
add a mechanism to allow custom waiters to take dynamic values at runtime by editing the waiter config on the fly
argument
field, which describes what's checked, this is the only place where we replace themapply this new capability in transforming appflow
wait_for_completion
code to use a waiter (follow-up on rewrite polling code for appflow hook #28869)