-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Bugfix/support Subpath w/o Execution API Url #57372
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
Bugfix/support Subpath w/o Execution API Url #57372
Conversation
vincbeck
left a comment
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.
Any way to cover this use case with a test?
At least I need to adjust existing tests to make CI Green, will push/fix some in a moment :-D |
AutomationDev85
left a comment
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 like.
Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
|
Looks good! thanks for this! |
We noticed that the execution URL needs to be added explicitly when deploying to a sub-path. This is a "burden" for Edge because other workers which are running inK8s (e.g. Celery) still benefit from an internal API endpoint.
If not provided the grepping of the execution API URL is now following the edge API URL per default and includes support of sub-path. Also the URL is logged (once) which makes error triaging easier.
FYI @dheerajturaga