Unsupported parameters for (setup) module: gather_subset, gather_timeout about ansible-pfsense HOT 7 CLOSED

After some googling, I discovered that gather_subset and gather_timeout are part of the built-in setup module (https://docs.ansible.com/ansible/latest/modules/setup_module.html) automatically called by playbooks. Sensing some namespace clashing here, I removed the collections: block from the play, and this worked:

- name: Configure pfSense
  hosts: pfsense
  remote_user: 'root'
  tasks:
    - name: General setup
      pfsensible.core.setup:
        timezone: America/Chicago

I was basing my usage on the example and subsequent comments explaining the new task name changes in #39. So perhaps some documentation clarity would help others avoid the same trap?

from ansible-pfsense.

Using collections: in a playbook just seems like a recipe for disaster. I'm not sure how one is expected to avoid namespace collisions using that.

from ansible-pfsense.

This is my first encounter with collections, so I was just trying to piece together how it's supposed to work. The ansible documentation specifically mentions using collections in playbooks, so it didn't seem that far-fetched since it wasn't working to begin with because ansible had no idea what I meant by pfsense_setup, and I didn't know the examples in the documentation were wrong.

from ansible-pfsense.

Part of the issue is that we have two versions of "ansible-pfsense" - this repository which was organized around eventual merging into ansible proper, and "pfsensible{.core}" which is structured like a collection. pfsensible is currently built by a script using ansible-pfsense as the source. There is no separate wiki docs for pfsensible yet.

from ansible-pfsense.

Ok, thanks for the info. I'll be watching with interest as I'm trying to ansible-ize as much of my pfSense install as I can, and will try to help out if I can.

from ansible-pfsense.

I've filed ansible/ansible#69195 to try to get some better clarification from ansible about module name collisions. However, I think we're going to want to switch the pfsensible.core module names back to the pfsense_ prefixed versions to avoid these collisions. I'm not sure that adding collections to the namespace search was an option when we first started on the pfsensible.core collection and I was wanting to avoid long module names. Having the search path avoids that.

We would need to announce the change well though as it will break existing usage, but now may be the time to do it.

from ansible-pfsense.

Will be keeping the pfsense_ module name prefixes.

from ansible-pfsense.