#mcollective

Does anyone know if its possible to pass arguments with spaces in it to the rpc agent?

I'm attempting to do something like: mco rpc my_agent do_stuff query="select foo from bar"

but I get "Could not parse --arg foo" as an error

there's nothing that prevents that from happening in the rpc application. it could be that your agent doesn't shellquote its arguments

@_rc its not even make it as far as sending the argument to my agent. mco rpc is barfing before it even connects to the collective

OK, so if I use --arg, it works

so: mco rpc --agent my_agent --action do_stuff --arg query="select foo from bar"

thats the actual argument that fails or are you sanatising it?

https://github.com/puppetlabs/marionette-collec... is doing the parsing and shouldn't barf on that

but maybe something is getting confused with whats a different argument to the mco command and so ARGV has some weird shit in it

if i want to connect to rabbitmq via ssl do i need to generate certs for MCollective and all of the nodes? The rabbitmq cluster is not using existing puppet certs unfortunatley

reuse your pupet certs

Volcane: that's not an option

the entire rabbitmq cluster was built with different certs and is already in production use

did u check if it even bothers to verify them against a ca?

cos then you can just use any certs if it doesnt

yes it checks

either make more iwth its ca or share

you can share the tls cert between nodes, its not ideal - but its not used by mco for any purposes

its more what your goals are with encrypting the node <-> rabbitmq traffic

if sharing a cert aligns with your needs, rock on.

the certs mco use for SSL security plugin can come from a different ca - or use puppets - even while you're using different ones for tls

ok thanks Volcane i'll see if i can get approval to have the mco traffic to rabbitmq be unencrypted. . . because it's not the reason we're encrypting anyway