forked from cds-snc/notification-api
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Upgrade marshmallow and marshmallow-sqlalchemy #1224
Labels
dependencies
Pull requests that update a dependency file
Dev Reviewed
Notify
PM Reviewed
QA Reviewed
QA
Comments
Hey team! Please add your planning poker estimate with Zenhub @cris-oddball @justaskdavidb2 @k-macmillan @kalbfled @ldraney @nikolai-efimov |
Please add your planning poker estimate with Zenhub @EvanParish |
20 tasks
kalbfled
added a commit
that referenced
this issue
Mar 19, 2024
…1224 #1225 Co-authored-by: Michael Wellman <[email protected]>
There are currently 63 test failing -
|
mchlwellman
added a commit
that referenced
this issue
Sep 11, 2024
PR approved and merged. All non-pinned dependencies were updated, but no Twistlock issues resolved. 1 dependabot issue was resolved. Sending to Perf. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dependencies
Pull requests that update a dependency file
Dev Reviewed
Notify
PM Reviewed
QA Reviewed
QA
User Story - Business Need
While working on #1222, upgrading marshmallow and marshmallow-sqlalchemy to the latest major versions resulted in successful build followed by runtime errors in multiple container. The tracebacks concluded with
ValueError: Couldn't import '<varies by container>': Invalid fields for <UserSchema(many=False)>: {'user_to_organisation', 'verify_codes_identity_provider_user_id', 'user_to_service'}
.User Story(ies)
As a VA Notify developer
I want to upgrade marshmallow and marshmallow-sqlalchemy
So that we minimize vulnerabilities and future upgrade pains.
Additional Info and Resources
Appears to be up to 9 classes/objects that would need tweaking:
Private Zenhub Image
There are numerous instances of this SAWarning which is coming from marshmallow-sqlalchemy; check to either make sure these aren't seen or refactor to remove these warnings.
Engineering Checklist
Acceptance Criteria
QA Considerations
Potential Dependencies
Leave blank if n/a
Out of Scope
Do not upgrade Celery or SQLAlchemy. Separate tickets exist for those upgrades.
The text was updated successfully, but these errors were encountered: