-
Notifications
You must be signed in to change notification settings - Fork 10.1k
Update remote.Client interface's methods to return diagnostics instead of primitive errors
#37502
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
a485b89 to
3a0406d
Compare
|
|
|
I learned what's required to run the Test results are below - I think that this is sufficient as the skip and failures are not due to this PR's changes.
|
e69068e to
65b3b88
Compare
|
I've run the tests for the |
|
Note for reviewers: I've run tests on the following backends:
|
65b3b88 to
2d86ba1
Compare
9ee326d to
d097dc6
Compare
…te calling code (incl. tests) to use diags.
307c1e2 to
8ec4eb2
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.
This is the place where the Put and Get methods are called by other Core code. All other calls to the affected methods in this PR are tests.
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.
This shows that any warnings returned are lost here, but we can update the calling code in future - I wanted to keep the scope of this PR minimal!
|
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 #37496
This PR updates the interfaces that are used for reading and saving state to/from remote locations. The changed code is used in all backends in the
remote-statefolder.By making these interfaces return diagnostics we allow backends to return warnings to users, instead of just errors.
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