invisible ansible

I would like to make ansible usage ‘invisible’ (due to some strange policies to use puppet even for the smallest stuff).

There are two problems about it:

  1. There is always an .ansible folder in the home directory. How can I switch this off (I’d rather not write a task to delete it afterwards)
  2. I am using local facts. I could not find the setting for the ansible local facts folder (/etc/ansible/facts.d) . I read somewher about an obscure 'fact_path' but there is no documentation about this variable/setting to be
    found in the docs.

Could you please help me
Thanks :)

I would like to make ansible usage 'invisible' (due to some strange
policies to use puppet even for the smallest stuff).

        mv ansible puppetthing
        mv ansible-playbook puppetotherthing

Sorry. I couldn't resist.

        -JP

Well, if you want to do it, do it right :D:

ln -sf /usr/bin/ansible /usr/bin/puppet

Seriously now, I would discourage you from breaking your policy. If you
believe your policy is not good, change (or fight for changing) your policy.

I sympathesize with the boss problem.

As such, may I suggest:

include ansible
require ansible

ansible::ansible::ansible {
before => stuff,
after => otherstuff,
requires => ansible::ansible,
what => “is most awesome”;;;
ensure => “my boss doesn’t find out”;;;
notify => “not my boss”
};; <=> # I’m not sure what the spaceship operator does but I like saying spaceship operator

Really, seems more to be an education issue. Having a CM framework is one thing, but say you need it for application deployment, provisioning, or speak to strengths in orchestration and then eventually he’ll let you use it for everything maybe :slight_smile:

Really, seems more to be an education issue.

The problem here is (as you surely know) that managers don’t have time for education. “We already bought the expensive product xyz support and we want anyone to use it as we already payed for it” .
There is also no way to explain anything. Nevertheless, the machines are not completely managed. So it’s not forbidden to login there via ssh and to do stuff. That is what I mainly use ansible for, as a (very well) trained monkey, who automates al the steps for me. (So the ansible binary is on my notebook).
The real question is:

Why does ansible require to leave traces like the .ansible directory in home folder?
Is there a way to change the facts folder?

``

since ansible needs the .ansible to execute its modules, the only way I see of “cleaning up” is running a raw task that deletes it in every playbook.​