Skip to main content

Remove an asset from the registry.

DELETE 
/api/assets/:id

The mirror of DELETE /api/sensors/{id}, and guarded the same way: that route refuses to delete anything that is not a sensor, and this one refuses anything that is not a force. Without the pair, either namespace could remove a row belonging to the other, and because the friendly whitelist is derived from registry membership, deleting an aircraft by side effect drops it off the whitelist — our own drone starts scoring as an unknown contact (invariant 10).

This did not exist, and its absence had a cost worth recording: with no route, a row could only be removed with psql, which bypasses the refreshes below. The runtime kept the deleted vehicle's payload sensors in its declared set, so a phantom <uuid>/eo-turret sat on the LIVE rail reading NO RETURNS, belonging to an asset that no longer existed.

Request​

Responses​

the asset is gone; a link issued for it alone is revoked with it