Replies: 2 comments
-
I'm not entirely sure what kind of behavior you are expecting with the alias and rule modules. As written, they are intended to fully define the alias or rule as described in the module parameters. Are you expecting to be able to only modify specific fields or add entries? Could you write an example play and give before and after definitions of the aliases/rules? No, you can't reference separators in a rule's before: or after: field. The separator locations are based on the rules, not the other way around. |
Beta Was this translation helpful? Give feedback.
-
To add and remove an alias works amazing, my question referes to the when clause "edit" When I use the playbook to manage an alias that blocks IP addresses, and there are 10 IP addresses currently listed, selecting when: add_or_edit_or_remove == "edit" causes the playbook to overwrite those 10 addresses with a single new entry. Is there a way to prevent this from happening? Here’s the relevant section of my playbook:
|
Beta Was this translation helpful? Give feedback.
-
Good afternoon @opoplawski
Thank you for developing this module. I have a couple of questions, and I hope this is the appropriate place to ask. If not, kindly point me in the right direction.
First, regarding the pfsense_alias module, is there a way to modify an existing alias without overwriting its current entries? When I attempted this, it replaced all the existing data with the new information.
Second, with the pfsense_rule module, when using the after: option, is it possible to specify a separator instead of a name or description?
Lastly, I’ve encountered a similar issue with firewall rules where attempting to edit an existing rule results in it being completely overwritten.
Thank you for your assistance.
Beta Was this translation helpful? Give feedback.
All reactions