Skip to content
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

Include route params in RpcHttp instance when http proxying is enabled. #9997

Merged
merged 2 commits into from
Apr 25, 2024

Conversation

kshyju
Copy link
Member

@kshyju kshyju commented Apr 11, 2024

Fixes #9840
Adding support for workers to request route params data populated in the RpcHttp instance when Http proxying is enabled.
Worker needs to include "RequiresRouteParameters" capability in the capability list they send to host during init/env reload request for this to happen.

Pull request checklist

IMPORTANT: Currently, changes must be backported to the in-proc branch to be included in Core Tools and non-Flex deployments.

  • [] Backporting to the in-proc branch is not required
    • Otherwise: Link to backporting PR - backport PR follows shortly.
  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • My changes do not require diagnostic events changes
    • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
  • I have added all required tests (Unit tests, E2E tests)

@kshyju kshyju force-pushed the shkr/9840_route_params_for_http_proxy branch from 2f1cd58 to 4e0d775 Compare April 15, 2024 22:38
Copy link
Contributor

@ejizba ejizba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested on a Node.js app and worked just fine!

@YunchuWang
Copy link
Contributor

Validated the change works in python http v2 app, can grab the route params from rpchttp and set into fastapi req
image
image
image

@kshyju kshyju requested a review from satvu April 22, 2024 23:40
@kshyju kshyju requested a review from fabiocav April 25, 2024 15:25
@kshyju kshyju merged commit 7ea046b into dev Apr 25, 2024
9 checks passed
@kshyju kshyju deleted the shkr/9840_route_params_for_http_proxy branch April 25, 2024 16:52
kshyju added a commit that referenced this pull request Apr 25, 2024
…d. (#9997)

* Include route params in RpcHttp instance when http proxying is enabled.

* Fixes to address PR comments.
kshyju added a commit that referenced this pull request Apr 27, 2024
…d. (#9997) (#10072)

* Include route params in RpcHttp instance when http proxying is enabled.

* Fixes to address PR comments.
fabiocav pushed a commit that referenced this pull request Apr 29, 2024
…d. (#9997) (#10072)

* Include route params in RpcHttp instance when http proxying is enabled.

* Fixes to address PR comments.
YunchuWang added a commit to Azure/azure-functions-python-worker that referenced this pull request May 6, 2024
Worker Changes to get route parameters of http invocation request from invocation request "route_params" attributes after host made update in Azure/azure-functions-host#9997.

TODO: Update lc test after lc image released with host version containing the change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Provide route params to worker when using http proxy
5 participants