We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Following PRs #346 #353 and #358 the refresh-mcollective-metadata cronjob still produces a file that mcollective is not able to correctly parse.
refresh-mcollective-metadata
Mcollective assumes all the facts will be top level keys. Instead they are now all nested under values. See #346 (comment)
values
A few options I could think of...
puppet facts
The text was updated successfully, but these errors were encountered:
argh :) and I first thought my mco facter filters are wrong.. I workaround this with an ugly sed:
|sed '3d' | sed 's/^ //'
Sorry, something went wrong.
I just change the command for refresh-mcollective-metadata cron in modules/mcollective/manifests/server/config/factsource/yaml.pp as follows:
cron { 'refresh-mcollective-metadata': command => "facter -p --yaml >${yaml_fact_path_real} 2>&1", ....
fix for voxpupuli#361
38bc7a8
6724b7f
fabd788
Successfully merging a pull request may close this issue.
Following PRs #346 #353 and #358 the
refresh-mcollective-metadata
cronjob still produces a file that mcollective is not able to correctly parse.Mcollective assumes all the facts will be top level keys. Instead they are now all nested under
values
.See #346 (comment)
A few options I could think of...
puppet facts
to extract thevalues
hash.The text was updated successfully, but these errors were encountered: