Repository navigation
Improve failure handling, identity validation, notification storage, and database configuration. - #2081
Merged
Conversation
Address tickets A08, A09, A10, A21, and A28 using the existing controller, repository, and configuration patterns. - Handle async and cleanup failures locally with controlled public errors. Registry hierarchy and creation failures return descriptive 400 responses with request references for server-side diagnostics. - Validate destination usernames within existing transactions and check final organization identity changes, without additional identity write guards. - Store notifications individually while retaining complete inbox responses and independent recipient identifiers; include the migration gitlink. - Share database configuration through the existing db helper. - Consolidate obsolete and duplicate tests while retaining regression coverage. Validation: 1,078 integration tests and 426 unit tests passed. Source/test lint reported no errors and four existing warnings; migration lint and generated OpenAPI checks passed.
jdalphond-mitre
approved these changes
Nov 3, 2026
jdalphond-mitre
left a comment
Collaborator
There was a problem hiding this comment.
There is a lot going on here. I did a bunch of manual testing which all returned expected results.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The changes prevent asynchronous failures from leaving requests unresolved, validate the final state of user and organization updates, remove the notification inbox document-size bottleneck, and align runtime and migration database targets.
Notification endpoints retain complete-inbox responses and require no UI changes.
Important Changes
npm run db:preflightto inspect the resolved target without connecting or exposing credentials. Reject conflicting database settings.Testing
bash -i -c "MONGO_DB_NAME=cve_test npm run test:integration:replicas"bash -i -c "npm run test:unit-tests"Deployment smoke checks:
Notes
Observable API changes:
ORG_HIERARCHY_FAILEDwith a request reference.ORG_CREATE_FAILED, with a request reference.USER_EXISTS, 403DUPLICATE_USERNAME, or 400ALIAS_COLLISIONresponses.e453293f, containing notification migration20261102-02. Stop notification reads and writes during conversion and avoid mixing old and new storage writers. Rollback can be refused if an inbox exceeds the old document-size limit.MONGO_CONN_STRINGoverrides and conflictingMONGO_DB_NAMEsettings now fail validation.