#mcollective

Then in the action:

cant say i ever tried :)

and eventually these things wont be ruby but see how it goes

Well hell, that works :)

Next problem...

If I do the cve args as options to the application, they get stored in the configuration as an array

In the agent, ie. the code that gets used directly if called with "mco rpc yum ..." then the cve args would be specified as eg. cve='foo bar', ie. a string

ok

So, do I convert the args from the app into a string as well?

foo.join(" ")

Yeah, that's what I mean

yeah

end of the day, what you would have typed on mco rpc .... has to be the API you call from the app

ie. replace configuration[:cve] (which will be an array) with a string

so if its gotta be a string you have to go send it a string

Yeah, OK. Just sorting it in my head

What kind of turtured genuis dreamed up this stuff?? :)

:)

*tortured genius

its the same for any cli talking to any API :) just not something ops people do much of i guess

It's a mindset

do have some ideas for a more natual feeling 'mco rpc' though

That makes things make more sense in my head when you say "api"

The agent is the provider and the application consumes it

yup, exactly, your agent is jsut a API

the DDL is just a API description - json schema, wsdl, swagger, etc, like all APIs have

mco rpc is a generic API client - apps are where you tailor the UI to your tastes if the rpc one doesnt do it for you

:thu

👍

(does that display on your client?)

shockingly yes hehe

Am assuming it's irccloud-specific

as long as its std emoji and not the bastardised app specific ones its fine they're just UTF8

ugh - another 3-year old bug: https://tickets.puppetlabs.com/browse/MCO-55

Any bright ideas how I can support "yum list [all,installed,updates,etc]" ?

Also, I'd like to make "mco yum list packages=kernel" respond the same as "mco rpc yum list packages=kernel"

<sigh> Can of worms!

respond the same as in same results display?

No, I needed to check for args with "=" in an parse them differently

One question - in the existing yum agent code, it does this:

Where does "request" come from ?

And how do I get stuff into request from the application?

request is the api call

mco rpc yum foo x=1

request[:x] would be 1

oh wait is this the agent?

where's the full file?

Let me push mr fork, as-is

*my

My WIP is here: https://github.com/yo61/mcollective-yum-agent/t...

and request stuff is in the agent?

yeah its just like i said request[:foo] is mco rpc yum action foo=1

'request' represent the API request over the wire with whatever properties you sent

So what do I put in the application to send foo=1 ?

c = rpcclient("yum")

c.thing(:foo => "1")

thing is the action

SO, could be c.send("the_action", {:foo: 1})

yes

👍

Am getting somewhere near now

Need to review everything again when I've not been hacking on it all day :)