Ok - this has been asked before, but I haven’t seen an answer, so I shall muster my optimism and ask it again in a new way.
I have a number of working automations that I can run from a button on a VMware VM. Things like adding CPU, RAM, new Disk, extending a disk. And all these work handsomely and I’m pretty stoked with all so far … but … (and that’s a big but, I cannot lie … ) because we charge money for additional RAM, CPU & storage, we need to have these automations run through the approval process, so engineers don’t give their managers bill shock at the end of the month.
My nifty automations all seem to work by way of /ManageIQ/System/Process/Call_instance, from what I can see in the automation.log file. I don’t see an automation_request object anywhere though, and I’m a little confused about what’s really going on there. Peter McGowan’s lovely little gitbook gives me the impression that every automation task magically gets a request, so if I construct an approval policy set for automation_requests, that should be all the magic I need. But It doesn’t seem to work. Maybe I just don’t understand the approval policy/profile stuff … or maybe I do and it’s not relevant because there is no request for these automations.
Somewhere else I saw it suggested that I need to explicitly generate an automation_request via the REST API … Is that so? Or am I over thinking this …?