#mcollective

I hope the PR to disable the refresh-mcollective-metadata makes it into the next release of the mcollective module.

I'm almost ready to fork the repo to disable it.

Before we were generating it from a puppet erb template, so it had the full puppet score in it.

well you can run the branch that it's been PRed from, assuming it wasn't a stale file

_rc, yeah.

and somehow I think those permissions I mentioned in puppet are messing us up, but there's no good way to control them since the files generated by the module.

stale branch I mean

well as I said, puppet doesn't consume that file, so it shouldn't matter in the slightest

but you can always just override plugin.yaml

_rc, that's what I thought too, but it uses that value to set the plugin.yaml in server.cfg and to generate the file in the script.

yes, and you can override anything that is done using mcollective::server::setting

so mcollective::server::setting { 'my facts plx': setting => 'plugin.yaml', value => $elsewhere, order => '70' }

_rc: passed travis https://github.com/puppetlabs/mcollective-sshke...

We use a few puppet variables in our hiera configs. Since we've moved over to the forge mcollective module, they're not all showing up. How can I query for servers that do not have 'servertype' set for instance?

bsg_kwolf: can you be more specific? Are you looking to have the puppet variables in your mcollective facts?

not sure how to do with the PL module. My module uses https://projects.puppetlabs.com/projects/mcolle... so you can pipe random variables into the facts

Ive got all our stuff fixed, I'm just missing a few servers. Trying to figure out which of the 489 are missing our variables.

pl one runs facter -p basically :(

I need something like 'mco find -S serverenv=''' but nothing I've tried works.

out of 489 servers, 455 have serverenv set. They should all have it set.

try “! serverenv”

jorhett, that did it. Thank you.