Looks like no.
You could uninstall ohai :)
On Tue, Aug 26, 2014 at 2:43 PM, kesten broughton <
kesten.brough...@gmail.com> wrote:
> Did this ever make it into trunk?
>
> I've hit a case where I'd like to be able to disable the automatic ohai
> fact-gathering.
>
>
> On Monday, March 17, 2014 11
Did this ever make it into trunk?
I've hit a case where I'd like to be able to disable the automatic ohai
fact-gathering.
On Monday, March 17, 2014 11:55:07 AM UTC-5, Michael DeHaan wrote:
>
> How about: default:
>
> fact_gathering=core,ohai,facter
>
> ?
>
> That way it's more pluggable-ish
>
>
How about: default:
fact_gathering=core,ohai,facter
?
That way it's more pluggable-ish
On Mon, Mar 17, 2014 at 12:42 PM, Brian Coca wrote:
> add ignore_ohai and ignore_facter =true (default false) to setup module
> and ansible.cfg?
>
> --
> You received this message because you are subs
add ignore_ohai and ignore_facter =true (default false) to setup module
and ansible.cfg?
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+uns
This is true that Ansible will use ohai if installed and doesn't
auto-remove it.
Your workaround right now would be to uninstall ohai.
I've pondered removing the facter/ohai integration in the past, though it
can be useful to help users migrating from other tools or having to still
work with them
Hi,
caveat - new to ansible.
I have a host that just happens to have chef client installed and is also
authenticating to an LDAP with 38,000 users in it.
When I run
$ ansible -m setup -i hosts hostname
it takes a very login time to return, because the ansible setup module is
finding ohai on
