Remove an asset from the registry.
DELETE/api/assets/:id
The platform stops being ours, which is a fusion decision as much as a bookkeeping one: the friendly whitelist is derived from registry membership, so the tracker starts treating its serial as an unknown contact again.
The guard is worth keeping in view. Deleting a row by side effect drops it
off the whitelist, and our own drone starts scoring as an unknown contact
(invariant 10). Before there was a route at all, a row could only be removed
with psql, which bypasses the refreshes: the runtime kept the deleted
vehicle's payload sensors in its declared set, and a phantom
<uuid>/eo-turret sat on the LIVE rail reading NO RETURNS.
Request
Responses
- 204
- 403
- 404
removed; a link issued for it alone is revoked with it
this workspace role is read-only
no asset with that id in this workspace