You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use the clc_firewall_policy module with state: present, I expect my Ansible task not to create a new firewall policy if the same policy already exists. The issue is, every time the Ansible playbook is run, a new firewall policy with the exact same settings (source, destination, and ports) is created. I can either check whether the policy already exists myself and skip the task (although I don't see anything in the clc-ansible-module documentation to support this either) or let it create duplicate policies and clean them up manually later.
This was initially raised in issue #13 and makes sense to implement in
the refactor of the ansible modules. If firewall_policy_id is
specified, search through the existing policies to determine if a policy
exists that matches the parameters passed to the model. If so, the
policy is not created.
When I use the
clc_firewall_policy
module withstate: present
, I expect my Ansible task not to create a new firewall policy if the same policy already exists. The issue is, every time the Ansible playbook is run, a new firewall policy with the exact same settings (source, destination, and ports) is created. I can either check whether the policy already exists myself and skip the task (although I don't see anything in the clc-ansible-module documentation to support this either) or let it create duplicate policies and clean them up manually later.The text was updated successfully, but these errors were encountered: