-
Notifications
You must be signed in to change notification settings - Fork 223
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
Is Marshmellow<3 required to function? #101
Comments
Ah, interesting. Looks like there's already a PR that would similarly solve my particular issue already in the works: https://github.com/Netflix/bless/pull/99/files |
Same here, thanks for this, it works |
@benjamin-hering I'm the guy that posed the question, glad that it helped. And yes, This PR fixes completely the issue, if we could fast-track the approval it would be great, also because as it stands the Lambda is broken and will not work at all without that fix. |
😂 haha so relatable. |
Netflix#101 wrong marshmallow was installed in the lambda zip file
I've started messing around with spinning up BLESS internally, but after a few iterations I got stuck on the following error popping up when I ran the lambda:
Anyway after a bunch of random Google-fu and stumbling through code. I ran across this comment by Jeremy Stott:
So (like any trained security professional) I simply blindly followed suggestions from random internet comments to try and get what I hope to be a critical security control for my org to work. Low and behold it works!
s/'marshmallow',/'marshmallow<3',/
got things back to a happy state. Here's my current setup.pyI've just started to familiarize myself with Bless, so I feel like I'm pretty strongly lacking in context for the full implications of this change here. Is this workaround of pinning to an earlier version of marshmellow the correct way forward?
The text was updated successfully, but these errors were encountered: