-
Notifications
You must be signed in to change notification settings - Fork 107
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
Retry Policy support for V2 #1253
Comments
Tasks completed - waiting for release - should be part of 4.25 |
Could any example be given on how to use retry policies on V2 functions? Everything I try results in no functions shown in the function app:
If i comment out the @app.retry() it works. Unfortunately I am unable to find any examples or documentation, or even references to possible options for the strategy in the python package. E.g. should strategy be fixedDelay or fixed_delay? Edit to make the confusion a bit more clear:
The URL in the docstring refers to a V1 function model documentation with camel case for things like maxRetryCount, which is converted to max_retry_count in Python (makes sense, but please add docs at least somewhere). Nowhere it states whether the input fixedDelay should now be turned into fixed_delay. Then we have the max_retry_count which is a number in the V1 model function.json files, but the V2 docstring states this has to be a string. It annoys me that I always have to blindly try all options with these things while all it takes is one simple example. Sorry for the outing of my frustration. WORKING EXAMPLE (for anyone referring to this thread later):
Conclusion, all names are converted from pascal to pythonic snake case and integers are converted to strings containing... integers. Good luck. |
Hi @ogiel, Thanks for the feedback and apologies for the confusion. As you mentioned, all names are snake cased. We'll definitely add some examples for retries with the v2 programming model. |
Tasks
The text was updated successfully, but these errors were encountered: