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

Roadmap to add more features? #48

Open
12 tasks done
spacewander opened this issue Dec 3, 2022 · 2 comments
Open
12 tasks done

Roadmap to add more features? #48

spacewander opened this issue Dec 3, 2022 · 2 comments

Comments

@spacewander
Copy link
Member

Currently, this extension already supports:

  • process HTTP request
  • send local response
  • get HTTP request headers
  • modify HTTP request headers
  • get HTTP request body
  • set HTTP request body
  • process HTTP response
  • get HTTP response headers
  • modify HTTP response headers
  • get all / set HTTP trailers
  • get HTTP response body
  • set HTTP response body

According to the proxy wasm spec, more features can be implemented. For example:

  • run Go when Envoy starts as a bootstrap extension
  • get/set Envoy property
  • interact with Go filters run in different workers via the shared data/queue
  • define/record metric

Will there be a plan to implement those features?

@doujiang24
Copy link
Member

doujiang24 commented Dec 18, 2022

run Go when Envoy starts as a bootstrap extension

This could be useful, but we are pushing this extension into envoy official repo: pull request 22573
(BTW, the new changes will also push envoy, after it is merged)
There is no bootstrap extension, according to Matt's requirement.

So, it may be delayed.

interact with Go filters run in different workers via the shared data/queue

I have no idea about the shared data/queue. could you help to give some points for refers?

get/set Envoy property
define/record metric

Yeah, these are planned, PRs welcome.

But, not a full detailed todo list yet.

@spacewander
Copy link
Member Author

I have no idea about the shared data/queue. could you help to give some points for refers?

I think about it again. We don't need it because unlike the Wasm filter, the data in Go filter is already shared between worker threads.

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

No branches or pull requests

2 participants