Rufio operations on a Workflow without Hardware #473

There is a case where a Hardware object doesn't exist but a Machine.bmc object does exist. In this scenario, auto discovery and enrollment would require manually creating a task.bmc object to get the hardware into a network or iso booting state. This is because Machine.bmc objects are referenced in Hardware objects and Workflow objects must go through Hardware objects in order to run BMC operations. It would be advantageous to be able to create a Workflow that references a Machine.bmc object directly. From there, auto discovery would create the Hardware object.