Update Rack Storage Item
hudu_update_rack_storage_itemIdempotent
Update an existing rack storage item in Hudu to change its mounted asset, unit positions, side, or power details.
Instructions
Update an existing rack storage item. A rack storage item is one thing mounted in a rack: it points at the Hudu asset it represents, occupies the units from start_unit to end_unit on one side of the rack, and carries its own power figures. The rack itself is a rack storage — use the hudu_*_rack_storage tools for the cabinet.
Only the fields you supply are sent. Be aware that Hudu applies these as a PUT: for fields you do send, the new value replaces the old one outright — read the record first with hudu_get_rack_storage_item if you intend to append rather than overwrite.
Operation class: Update. Impact: Overwrites the supplied fields on this rack storage item.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric Hudu id of the rack storage item. | |
| side | No | Which face of the rack the item is mounted on. The spec contradicts itself on this field: the list filter documents it as the string "Front" or "Rear", while the create and update body documents it as an integer with no published mapping. This argument follows the body and takes an integer. The only reliable way to learn which integer means which face is to read an item you know the physical side of with hudu_get_rack_storage_item. | |
| status | No | Status code for the item, as an integer. Hudu publishes no list of legal values and no meaning for any of them, so copy a value from an existing item instead of choosing a number. | |
| asset_id | No | Numeric id of the Hudu asset this mounted item represents — the device record carrying the serial, model and custom fields. Resolve it with hudu_list_assets, or read it with hudu_get_asset. The item record also returns asset_name and asset_url for display; those are outputs, not ways to identify the asset when writing. | |
| end_unit | No | The other end of the unit range this item occupies. Two properties of this range are not documented, and assuming either will place hardware in the wrong slot. First, direction: the API never says which physical end of the cabinet holds the lowest-numbered unit, so bottom-up and top-down are equally consistent with the spec. Second, inclusivity: it does not say whether a 2U device starting at unit 10 ends at 11 or at 12. Read an existing item from the same rack with hudu_list_rack_storage_items, compare it against hardware whose height you already know, and follow whatever convention that instance uses. Overlap is undocumented too — no conflict response is published for these endpoints, and create and update document only 422 "Unable to process request" — so do not rely on Hudu refusing to double-book a unit. | |
| company_id | No | Numeric id of the company this item belongs to. Note that the list tool documents no company filter, so this scopes the record without giving you a way to select on it later. | |
| power_draw | No | Power this item draws, for planning against the rack's `max_wattage`. The spec gives no unit for it at all. Hudu states no unit for this number, so it is comparable with other values from the same instance and with nothing else. | |
| start_unit | No | One end of the unit range this item occupies, in the rack's own numbering, which begins at that rack's `starting_unit` and so is not necessarily 1-based. Two properties of this range are not documented, and assuming either will place hardware in the wrong slot. First, direction: the API never says which physical end of the cabinet holds the lowest-numbered unit, so bottom-up and top-down are equally consistent with the spec. Second, inclusivity: it does not say whether a 2U device starting at unit 10 ends at 11 or at 12. Read an existing item from the same rack with hudu_list_rack_storage_items, compare it against hardware whose height you already know, and follow whatever convention that instance uses. Overlap is undocumented too — no conflict response is published for these endpoints, and create and update document only 422 "Unable to process request" — so do not rely on Hudu refusing to double-book a unit. | |
| max_wattage | No | Power ceiling recorded for this mounted item. As with the rack field of the same name, the spec names the quantity as wattage but never states the unit. Hudu states no unit for this number, so it is comparable with other values from the same instance and with nothing else. | |
| reserved_message | No | Free-text message carried on the item. The spec documents it only as "the reserved message for the rack storage item" and says neither when Hudu displays it nor what marks an item as reserved. | |
| rack_storage_role_id | No | Numeric id of the "rack storage role" this item takes. Read this carefully: it is NOT the rack the item sits in. The spec documents it as "the unique ID of the rack storage role", and the item record echoes rack_storage_role_name, rack_storage_role_description and rack_storage_role_hex_color beside it, so a role behaves as a named, colour-coded classification of the mounted thing. No endpoint lists the available roles and no schema defines one, so take an id from an existing item via hudu_list_rack_storage_items rather than expecting to look one up. |