Skip to content

Unlike in other SDKs, there is no link between RootContext and HttpContext / StreamContext #6

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

Closed
yskopets opened this issue Apr 20, 2020 · 3 comments · Fixed by #34
Closed

Comments

@yskopets
Copy link
Contributor

Summary

  • Due to a missing link between RootContext and HttpContext, it's not possible to to apply to HttpContext configuration that was set in the RootContext during proxy_on_configure
  • Why is HttpContext gets created by a standalone factory function rather than by RootContext ?
@mileswilson
Copy link

I'm also trying to understand how to solve this problem, and pass configuration to my HttpContext.

@dgn
Copy link
Contributor

dgn commented Aug 20, 2020

I just wasted a bunch of time on this. If the callbacks would accept closures with environment captures, this wouldn't be an issue

unleashed pushed a commit to unleashed/proxy-wasm-rust-sdk that referenced this issue Oct 29, 2020
…llow `RootContext` propagate configuration into `HttpContext`/`StreamContext` (proxy-wasm#6)
@bangau1
Copy link

bangau1 commented Nov 12, 2020

I am also trying to reading configuration and pass it into HttpContext, but can't do that.
I notice that this article https://docs.eupraxia.io/docs/how-to-guides/deploy-rust-based-envoy-filter/ use forked version which basically let the RootContext create the HttpContext (so can inject the configuration to them). For now, I am using the article approach (the forked version)

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 a pull request may close this issue.

4 participants