Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ufw tags needed on the firewall tasks #453

Closed
hvisage opened this issue Dec 28, 2015 · 2 comments · Fixed by #460
Closed

ufw tags needed on the firewall tasks #453

hvisage opened this issue Dec 28, 2015 · 2 comments · Fixed by #460

Comments

@hvisage
Copy link

hvisage commented Dec 28, 2015

Hi there,
as I do my own firewalling and don't want ufw to interfere, I run the playbook with --skip-tags=ufw, but found several places that needs extra tags: ufw:

TASK: [xmpp | Set firewall rules for Prosody] *********************************
failed: [] => (item=5222) => {"failed": true, "item": 5222}
msg: Failed to find required executable ufw

Places added: (grep -n ufw places):
roles/vpn/tasks/openvpn.yml:138: tags: ufw
roles/xmpp/tasks/prosody.yml:46: tags: ufw
roles/mailserver/tasks/dovecot.yml:93: tags: ufw
roles/mailserver/tasks/postfix.yml:74: tags: ufw
roles/ircbouncer/tasks/znc.yml:67: tags: ufw

@jplock
Copy link
Contributor

jplock commented Dec 28, 2015

Would you mind submitting a pull request?

@hvisage
Copy link
Author

hvisage commented Dec 28, 2015

Yes I do mind ;(
Bug me again in the new year then I’ll make some time to do the whole fork/etc. stuff (I’m a sysadmin, these gitting still gets to me …)

On 28 Dec 2015, at 5:13 PM, Justin Plock notifications@github.com wrote:

Would you mind submitting a pull request?


Reply to this email directly or view it on GitHub #453 (comment).


Hendrik Visage
Envisage Systems / Envisage Cloud Solutions
084-612-5345 or 083-675-5506
hvisage@envisage.co.za

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants