Skip to content

Allow using empty vm_id to indicate the current WasmVM. #138

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

Merged
merged 1 commit into from
Mar 8, 2021

Conversation

PiotrSikora
Copy link
Member

Signed-off-by: Piotr Sikora [email protected]

@PiotrSikora PiotrSikora requested a review from mathetake March 5, 2021 00:49
@PiotrSikora
Copy link
Member Author

I have integration tests in Envoy ready and passing, but the Envoy PR is blocked on envs update being merged first.

Copy link
Contributor

@mathetake mathetake left a comment

Choose a reason for hiding this comment

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

Nice, LGTM. Will this be a part of the next ABI?

@PiotrSikora
Copy link
Member Author

Nice, LGTM. Will this be a part of the next ABI?

This is more of a bugfix for the current version, really. Right now you need to pass vm_id of your own WasmVM (!) in proxy_resolve_shared_queue(vm_id, queue_name, &token) calls, otherwise it won't find the queue.

That call was originally added to support Shared Queue resolution across different WasmVMs (i.e. with different vm_id), but it seems that people are using it for local resolution as well, and then the plugin needs to know the host-assigned vm_id, which is definitely unnecessary.

@PiotrSikora PiotrSikora merged commit 217320a into proxy-wasm:master Mar 8, 2021
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.

2 participants