Skip to content

Conversation

@jscheffl
Copy link
Contributor

@jscheffl jscheffl commented Oct 27, 2025

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

@boring-cyborg boring-cyborg bot added area:providers kind:documentation provider:edge Edge Executor / Worker (AIP-69) / edge3 labels Oct 27, 2025
@jscheffl jscheffl requested review from eladkal and vincbeck October 27, 2025 20:21
Copy link
Contributor

@vincbeck vincbeck left a 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?

@jscheffl
Copy link
Contributor Author

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

Copy link
Contributor

@AutomationDev85 AutomationDev85 left a 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>
@jscheffl jscheffl merged commit 67fdf36 into apache:main Oct 28, 2025
76 checks passed
@dheerajturaga
Copy link
Member

Looks good! thanks for this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:providers kind:documentation provider:edge Edge Executor / Worker (AIP-69) / edge3

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants