Replies: 1 comment 2 replies
-
|
Thank you for the poll! I'm rather new to using this wonderful module - as my previous opnsense mgmt was a combination of shell + curl commands. I voted for 2nd option (No for all modules unless enabled by user). My rationale was to allow consideration of services whereby the service configuration has a manual component i.e. not provided or possible by the GUI. Example of such cases can be wazuh-agent, caddy, Tailscale plugins - at least true for my environment. Here, my assumption is that a auto-reload (if default: ON) would erase the manual configuration components (e.g. fields not supported by GUI). |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
As @ptoal mentioned in #238 => for Ansible-Modules it might make more sense to disable the automatic reload/apply of changes!
Currently all modules apply changes automatically, is some were detected.
We initially added this functionality as users of the modules were confused why their changes did not work.
If this is not the case all users will have to either:
module_defaults.reloadvaluereloadvalue of specific module-callsAs we also have 'multi'-modules that are able to change hundreds of entries at once, the automatic reload might make more sense there. That's why we added it specifically to the poll.
Users already have to manually disable the reload/apply in some cases if they perform an Ansible-loop
3 votes ·
Beta Was this translation helpful? Give feedback.
All reactions