-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add ability to use extra_ghetto_ipsets #14
Comments
I think we should just continue using the concept of For instance:
So, we'll have two sections, one for the normal |
This only causes problems because we treat web and ssh as special... but if you use them with extra iptables rules we would only need to check them where we process the extra rules:
But ugh... none of this is just simple and obvious, and actually will end up causing more problems. I dunno, it will start to outweigh the benefits. Perhaps a better question is if we need to streamline the way we run the iptables rules in the first place. |
extra_ghetto_ipsets var. allows you to add additional ipsets which will then be used to create extra firewall rules. Unfortunately, extra_ghetto_ipsets only works with extra_iptables_rules because of the extra variable checks added, otherwise you might end up with 'AnsibleUndefinedVariable' errors or missing attributes in dict object errors. This commit is related to issue #14 on GitHub[1]. 1. #14 Signed-off-by: James Oguya <[email protected]>
Right now ipsets are defined in our global (private) variables, but hosts can override them by copying the entire dict structure from
private/vars/ipsets.yml
to their host_vars and adding custom hosts. Unfortunately if the global ipsets change for some reason, we would probably forget to update the overridden ones too.It would be nice for a host to be able to use something like
extra_ghetto_ipsets
, similar to how we useextra_iptables_rules
.The text was updated successfully, but these errors were encountered: