Closed noah-tutt-praetorian closed 2 weeks ago
This value is already provided by the username
field. Why does it need defined twice?
Those two values don't have the same meaning - one is a type, and the other is a specifier. Currently, we only support one of these types of integration (on the frontend, the backend will support any number), but the specifier still needs to be populated with a value.
I'm open to any other naming scheme, there just needs to be some value there, and preferably one that makes sense for search.
Maybe we let the user specify?
@storbeck more elegant solution here: https://github.com/praetorian-inc/chariot-ui/pull/69
Summary
Ensures that
value
is set for relevant integrations. This prevents the issue noted in https://github.com/praetorian-inc/chaos/pull/850. Also ensures that results from these integration are searchable.Type
Bug Fix