James Keller (US)
Day-2 and Delete Actions have some limitations that cause bloat, duplicate self-service actions, and a poor user experience:
  • Allowing Day-2 Actions to be associated with multiple blueprints: Day-2 actions can only be associated with a single blueprint, meaning executing the same action on different blueprints requires multiple actions. Not associating the action to a blueprint loses functionality like not appearing in catalog pages or ownership based RBAC.
  • Make the .entity field part of the form: moving the .entity field to be part of the form would allow filtering for entity lists that are too long to search through manually. It would enable many previously impossible form configurations while still having the blueprint association and features that come with that. Workarounds have the same problem as above: loss of functionality.
  • Better search / filtering: Certain types of queries are not possible in the entity search section of Day-2 actions. Expanding this to function more like policy queries would expand functionality.