feat: Enhance volume management with dynamic reload and improved error handling #17
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
Comprehensive improvements to volume management functionality with support for dynamic reload, robust attachment validation, and complete error notifications to clients.
Changes by Commit
1. fix: Improve volume persistence schema safety
CREATE TABLEtoCREATE TABLE IF NOT EXISTSfor volumesCREATE INDEXtoCREATE INDEX IF NOT EXISTSfor both indicesDROP TABLE IF EXISTSthat could lose data in production2. feat: Add dynamic volume reload functionality
AsyncMailCore.reload_volumes()method for runtime reconfigurationPOST /volumeandDELETE /volume/{name}protocolfield (genro-storage standard)3. feat: Improve error handling and client notifications
ValueErrorhandling for attachment fetch failuresRequestValidationErrorexception handler with detailed logging4. test: Fix volume tests for account_id requirement
test_message_rejection_invalid_volumeaccount_idfield to test messagestest_volume_api_endpointsBenefits
Testing
All changes have corresponding test updates and have been validated against a running service instance.
Generated with Claude Code