Repository navigation
Conversation
| AttachStatus string | ||
| } | ||
|
|
||
| func (s *Service) Attach(id string, input AttachVolume) error { |
There was a problem hiding this comment.
Volume actions are currently modeled as direct state transitions on the volume repository. This keeps the MVP lightweight, but this file is where future backend/provider behavior would likely attach.
| return s.setVolumeStatus(id, "available") | ||
| } | ||
|
|
||
| func (s *Service) ExtendSize(id string, newSize int) error { |
There was a problem hiding this comment.
Extend updates size and timestamp without modeling asynchronous resize progress. That is a deliberate compatibility shortcut to keep this slice focused on API shape and observable state.
| return s.setVolumeStatus(id, input.Status) | ||
| } | ||
|
|
||
| func (s *Service) setVolumeStatus(id string, status string) error { |
There was a problem hiding this comment.
setVolumeStatus centralizes the simple status-only actions. Similar action handlers in the API layer can be reviewed by checking which action maps to which status transition here.
a23d09d to
ac36a97
Compare
6c507e9 to
9ee66c6
Compare
|
Closing without merge. The repository was reset to a new root that keeps only the retained design decisions (see |
1 participant
Summary
Main Review Points
Verification