Store all RequestMetadata for filtering Operations
Before raising this MR, consider whether the following are required, and complete if so:
-
Unit tests -
Metrics -
Documentation update(s)
If not required, please explain in brief why not.
Description
This MR adds support for storing the previously unused action_mnemonic
, target_id
, and configuration_id
RequestMetadata
fields in the database, as well as support for using these new fields when filtering Operations with a ListOperations
request.
The MR adds a new table for request metadata, with existing data from the operations
table copied across and the old columns dropped. This allows us to deduplicate the metadata we're storing, and decouples it from the operations
opening up the possibility of tracking metadata for other request types in the future.