It is possible that a user wants to define some arbitrary data for a step in its configuration to later use it within a hook to execute custom logic.

Therefore my proposal would be to extend the DriveStep with an arbitrary data-property in order to allow for such use-cases