Activate the post-update hook when the param is true

[kampfschlaefer]

regardless whether the repository is freshly created or not.

[zuazo]

It seems that this breaks why-run support, doesn't it?

[kampfschlaefer]

Probably.

I have to admit that I have to read up on why-run...

[kampfschlaefer]

No, it shouldn't break why-run as far as I see it as the cookbook_file resource supports why-run already. It will show up as another dynamically defined resource though.

When argumenting small resources, a point could be made to create a new resource/provider for the post-update-hook. And for adding more custom hooks.

[zuazo]

What I mean is that in case the hook is updated, it will not mark the resource as updated because it's outside the converge_by. But maybe this is the desired behavior. I have doubts.

[kampfschlaefer]

Well, the desired behaviour is to create the hook even if the repository is already there. So it should be outside the unless-block. I will try something else.

[zuazo]

Yes, but if the hook is updated but not the bare repository, should the git_ssh_server_bare resource fire the notifications (the notifies)? If the answer is yes, the hook code should go inside another converge_by block.

[kampfschlaefer]

The resource and action is to create a repository, I think its okay not to fire the notifications when the hooks change.

[zuazo]

OK. Sounds good. Thanks for another PR 😉

[zuazo]

Released in 0.3.0.