-
Notifications
You must be signed in to change notification settings - Fork 10.1k
Update backend.Backend's StateMgr method to return diagnostics instead of primitive errors
#37496
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
Conversation
390e471 to
e501728
Compare
|
Testing:
|
…rrors via diagnostics
…agnostics are defined in the context of the config they're triggered by
…nvalid_mode` by making `diagnosticBase` struct comparable
e69068e to
65b3b88
Compare
|
I just rebased this PR on top of X so that the s3 test failures resulting from diagnostic comparisons are resolved. This means it's easier to see what failures could be caused by this PR's changes. I ran the |
|
I ran the
|
|
Note for reviewers: I've run tests on the following backends:
|
…ific comparer code to s3 package
…ue from StateMgr method
65b3b88 to
2d86ba1
Compare
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
This PR is stacked on #37509
This PR updates the backend.Backend interface's StateMgr method to return diagnostics instead of errors. This will allow backends to return warnings in future, instead of just errors.
I've also updated any calling code that uses any implementations of that method. This includes test code.
Target Release
N/A
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry