Evgeni Golov

For packaging topics, please ping @theforeman/packaging

This sounds reasonable indeed. Do you want to prepare a PR? Please note, there is (intentionally) no default here in the module/role, so adhere to the default of the server....

To keep things logged properly, Marko, @jeremylenz and myself discussed this a bit further and got to a point that we think the following two changes could be beneficial: *...

Hmm, can't repro with the following playbook: ``` --- - hosts: localhost tasks: - name: product theforeman.foreman.product: name: Test Product organization: Default Organization server_url: https://foreman.example.com/ username: admin password: changeme validate_certs:...

Yeah, it flips fine between enabled and disabled for me, but it also reports product as always changed, weird

The file needs to be on the remote server too. But why are you using a remote server anyway?

There is no need for remote execution if the Ansible node can reach the Foreman servers via HTTPS. You can use `hosts: localhost` and `server_url: https://foreman example.com` just fine. If...

How do you set it? It should fetch it from the env, we even have a test for that: https://github.com/theforeman/foreman-ansible-modules/blob/53d1a6b2b2c6d423fd910631ab79fcef9b1ff8f9/Makefile#L109

And the rest? And the playbook?

Mhh… ```console % env |grep FOREMAN % cat test.yml --- - name: Test play hosts: localhost tasks: - name: Create Admin group theforeman.foreman.usergroup: name: Admins admin: true state: present %...