Thomas Woerner

I tried to verify your issue. I have deployed the server on a 7.9 and also successfully deployed a replica on a 8.6. I have used ansible-core-2.12.7-1. Please provide more...

Which ansible-freeipa version are you using? I tried to replicate your issue with version 1.8.2 and also older versions, but `state: present` is not touching the disabled state with `nsaccountlock`...

This is a result of using the server context that ansible-freeipa plugins are using by default. I opened a ticket for IPA https://pagure.io/freeipa/issue/9097 For now you can use the client...

On 4/22/22 17:17, Rafael Guterres Jeffman wrote: > Currently, our module documentation use: > > |`(...) module is as compatible as possible to the Ansible upstream ` | > >...

It is indeed a list, but it is possible to use single string that is used like ["single string"].

The issue is that the underlying ipa server code is not able to easily handle the rerun case. The client role is able to be run again with the repair...

To make the server and also the replica role idempotent it is needed to compare the actual configuration of the services to the needed configuration for IPA. After this has...

`action: ` is the default for all modules that support the action parameter. The documentation of the `group` module has this: > `action` controls if a the group or member...

Please add examples to the EXAMPLE section of the module and also example playbooks in the playbooks folder.

bind is allowing to specify the port for a forwarders with "port " additionally to the IP addresses. But dnspython that is used to verify the list of forwarders (nameservers)...