set cache_valid_time=0 to ensure an apt-get update after the added repo-key

[lhoss]

I set cache_valid_time=0 to ensure that an apt-get update after the added repo-key
else you often get 'WARNING: The following packages cannot be authenticated!
See also: http://askubuntu.com/questions/75565/why-am-i-getting-authentication-errors-for-packages-from-an-ubuntu-repository

ps: following might be related ansible issue: ansible/ansible-modules-core#1497
I'm running currently with ansible v1.9.2 (on Mac, installed using brew)

and following role issue might have the same cause:
#21

[dj-wasabi]

Thanks!

[kostyrev]

@lhoss why on Earth did you push this very same role to galaxy?

[lhoss]

Hi!
ok, I removed it again.

My idea was to use ansible galaxy (for the provisioning) with my own fork
as I expect more customizations might be needed.
I'm aware that for now, my branch is up2date with Werner's (also thx to
his quick merge of my bug-fix PR), so it looks/ed silly.
So, in case I'm actually extending my fork, would it be ok/recommended to
publish on ansible galaxy?

One idea to avoid seeing too many published forks (like I just did) would
be to provide a way to make a role private (non published/searchable).
In any case maybe the Galaxy Doc. should be updated with some 'best
practices' here.

So for now, I will use ansible-galaxy with the git+https Url dependency.

best,
Laurent

ps: On a side note, getting following released, will be very very helpful also:
ansible/ansible#10620

make ansible-galaxy version work for branches as well as tree-ish

[kostyrev]

So, in case I'm actually extending my fork, would it be ok/recommended to
publish on ansible galaxy?

Don't get me wrong!
You _can_ do whatever you want to do. It's a free world we're living in (ok, not so free but whatever).
I just get upset when I try to search some role in galaxy and I have to scroll over and over again through all those forks of the very same role one guy wrote. And I think to myself "maybe that guy abandoned his role" but then I get to his github and no, the role is actively supported. And that's very frustrating.
Yeah, there are times when your proposed changes were not merged yet into upstream.
For those cases I have

- src: https://github.com/kostyrevaa/ansible-zabbix-agent.git
  name: dj-wasabi.zabbix-agent
  path: roles

And then I pursue the upstream's author to get a look at my stuff.
If it gets merged I just change src

- src: https://github.com/dj-wasabi/ansible-zabbix-agent.git

I just don't see the point:
even when your proposals are not merged yet why bother to publish it to galaxy.

[lhoss]

Yeah I agree!
and thx for the tip (yeah using the 'name' is a good idea)

anyway: I hope the Ansible ,euhh redhat guys pimp a bit the management
with ansible galaxy..

[kostyrev]

Yeah, galaxy is a... hmm.. you know