11ea8d533d
Enforce no hold group when creating hold object When a hold is created by build_object, it's auto-assigned a hold_group_id (as expected). When a hold is ->fill, it's hold_group_id is cleared by cleanup_hold_group (as expected). The problem is then this causes the object before ->fill to be out of sync with the up to date object returned by the API (i.e. the latter has an empty hold_group_id, as expected, but the former has the auto-assigned hold_group_id). Using ->discard_changes or ->get_from_storage doesnt work because the became a after ->fill. Signed-off-by: Lucas Gass <lucas@bywatersolutions.com> |
||
|---|---|---|
| .. | ||
| v1 | ||