cccs-rs

For sure! The one thing I noticed is the output is more nested under MACO which I believe wasn't the case for CAPE, so maybe flattening is required?

What do you think about having the data transform back to a flattened state for presentation in the UI? I can amend my PR to include that change specifically for...

@kevoreilly @doomedraven thoughts?

The problem that I noticed with creating a translation layer from CAPE-to-Maco, let's say for an export API, is that there isn't a standard for the CAPE output (least not...

Right, which can be doable if let's say all parsers agreed on using the same set of fields rather than a parser defining fields at will (which is the aspect...

Based on the APIs, whenever you delete a signature source, it should consequently remove all the signatures related to that source: `delete_signature_source` (Update Source Managment page): https://github.com/CybercentreCanada/assemblyline-ui/blob/20a98c26f9e00804870ca01074c44f52acfd9fcd/assemblyline_ui/api/v4/signature.py#L329 `set_service` (Services page):...

It's possible the service didn't get the new bundle of signatures from the updater at the time of the task. Services usually ask if there's a new bundle after each...

So in this case, you'd like to have some kind of menu that appears when a URL is inputted that allows you to specific the proxy to egress from? Quick...

Current render of providing egress options in to the UI (only when a URL is given):  Example config: ```yaml config: ... ui: url_egress_proxies: CANADA: https: a GeRMANY: http: b...

The current implementation allows you to specify the proxy dict that gets passed to the Requests library. So it would be possible to have a configuration like: ```yaml config: ......