Need to support keyword attributes in action calls

[abellotti]

For the Automate usage, users call model methods with just the arguments as needed.

From the API server usage, we're expecting the json representation,

for example, in the model:

ar = AutomationRequest.find(15)
ar.authorized?(userid)

From the API server side, to expose authorized?, we'd take in a user reference or userid,

miq.automation_requests.find(15).authorized?(:userid => userid)

However, the expectation, is that the following would work:

miq.automation_requests.find(15).authorized?(userid)

The API Server needs to be able to expose keyword name list for method and when the client defined such actions, it would be able to check for hash signatures or otherwise treat them as an array of parameter. In the latter case, the Client would convert the array to the proper json to send up to the server.

[mkanoor]

@abellotti
In Ruby the method object has a method called parameters which gives you back the arguments of the method in order.

e.g.

def my_method(name, age, state="NJ")
puts "#{name} aged #{age} lives in the state of #{state}"
end

method(:my_method).parameters

=> [[:req, :name], [:req, :age], [:opt, :state]]

This way the post can send the JSON arguments in any order but once we get it on our side we can pass it in correctly. So as long as the parameter names used in the API client are using the same names as the one in AR models we should be able to invoke them