Hi,
In the latest facter version I see the facts value format is nested like
below,
system_uptime => {"uptime"=>"415 days", "days"=>415, "seconds"=>35903914,
"hours"=>9973}
But how can we do this facts based filter with mco query when we have
nested format. For example if I want to perform
hmmm. so you meant to say there is no way to filter with nested facts
right?
But found something on https://tickets.puppetlabs.com/browse/MCO-363 and
not sure if this something what am expecting.
Thanks
Ravi
On Saturday, March 11, 2017 at 11:25:24 PM UTC+5:30, R.I.Pienaar wrote:
>
>
>
>
ohh.. Then I may have to downgrade the facter to little lower version make
use of all the facts through mcollective.
Do you think any solution for this with the latest facts version with
nested structure? If not then the only way to downgrade it.
Regards
Ravi
On Sunday, March 12, 2017 at
Am using facter version 2.4.6 and it says invalid option.
[root@mco-console ~]# facter --show-legacy
invalid option: --show-legacy
[root@mco-console ~]# facter --version
2.4.6
[root@mco-console ~]#
Regards
Ravi
On Sunday, March 12, 2017 at 12:36:08 PM UTC+5:30, michael.smith wrote:
>
> The
On Sun, Mar 12, 2017, at 07:50, rakare2...@gmail.com wrote:
> ohh.. Then I may have to downgrade the facter to little lower version
> make
> use of all the facts through mcollective.
>
> Do you think any solution for this with the latest facts version with
> nested structure? If not then the
I tried as you said and below the registrationmonitor.rb content.
# discovers against directory of yaml files instead of the traditional
network discovery
# the input must be a directory of files as written out by the
registration-monitor plugin
require
> On 11 Mar 2017, at 09:35, rakare2...@gmail.com wrote:
>
> I tried as you said and below the registrationmonitor.rb content.
Not sure. You will have to do your own debugging. Add logging lines and see
what goes wrong
I don't know this plugging really
>
>
