-
Notifications
You must be signed in to change notification settings - Fork 3
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
IWF-405: Rename failure handling API #67
Conversation
workflow_id, "", type_hint | ||
) | ||
|
||
def wait_for_workflow_completion( |
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.
this is also a rename same as in Java SDK.. too lazy to open a ticket for that (🥹 )https://github.com/indeedeng/iwf-java-sdk/blob/main/src/main/java/io/iworkflow/core/Client.java#L339
iwf/workflow_state_options.py
Outdated
""" | ||
execute_failure_handling_state: Optional[type] = None | ||
execute_failure_handling_state_when_retry_exhausted: Optional[type] = None |
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.
NOTE: python uses a different pattern as we mentioned this morning. we have wrapped a higher level model on the workflow state.
iwf/workflow_state_options.py
Outdated
@@ -87,14 +114,25 @@ def _to_idl_state_options( | |||
res.execute_api_retry_policy = options.execute_api_retry_policy | |||
if options.execute_api_timeout_seconds is not None: | |||
res.execute_api_timeout_seconds = options.execute_api_timeout_seconds | |||
if options.execute_failure_handling_state is not None: | |||
if options.execute_failure_handling_state_when_retry_exhausted is not None: |
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.
Should we make the naming more consistent like in the JavaSDK?
wait_until_api_failure_policy_when_retry_exhausted
execute_api_failure_policy_when_retry_exhausted
?
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 am thinking on that too. We can't do exactly because python sdk is using a differetn model and Python don't use the same convention like Java.
Maybe:
- proceed_to_state_when_execute_retry_exhausted : state_class
- proceed_to_execute_when_wait_until_retry_exhausted: bool
Our java SDK is :
- setProceedWhenExecuteRetryExhausted
- setProceedWhenWaitUntilRetryExhausted
WDYT?
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.
Makes sense to me 👍
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.
Done
No description provided.