-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[TT-162] Fix JSVM session metadata usage #3231
[TT-162] Fix JSVM session metadata usage #3231
Conversation
Can we add simple test for this? |
f50540a
to
5583dcd
Compare
Added tests and rebased the changes 👍 |
8da590d
to
91a7619
Compare
91a7619
to
acf46a4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/release to release-3-lts |
Working on it! Note that it can take a few minutes. |
* mw_virtual_endpoint: use map[string]interface{} for JSVM session metadata * mw_virtual_endpoint: improve test helper and session metadata test coverage (cherry picked from commit 3c1de7b)
@matiasinsaurralde Succesfully merged |
/release to release-3.1 |
Working on it! Note that it can take a few minutes. |
@matiasinsaurralde Seems like there is conflict and it require manual merge. |
Am testing with v3.1.2 but I think this issue is partially fixed. Getting
I suspect it's because of the struct declaration on line 56 |
Fix for #3218.
Description
When
use_session
is enabled, theSessionMeta
object is expected to contain a content with the following structure:Because we were previously using
map[string]string
, the key request and user fields break the unmarshalling step.Using
map[string]interface{}
fixes the issue.Related Issue
#3218.
How This Has Been Tested
Steps described in #3218.
Screenshots (if appropriate)
Types of changes
Checklist
fork, don't request your
master
!master
branch (left side). Also, you should startyour branch off our latest
master
.go mod tidy && go mod vendor
go fmt -s
go vet