# 389 Directory Server - Ansible Collection Question

**URL:** <https://forum.ansible.com/t/389-directory-server-ansible-collection-question/36600>\
**Category:** Ansible Developer\
**Tags:** fedora, galaxy-ng\
**Created:** [May 6, 2022, 4:24am UTC](https://forum.ansible.com/t/389-directory-server-ansible-collection-question/36600 "2022-05-06T04:24:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Simon\_Pichugin](https://avatars.discourse-cdn.com/v4/letter/s/f17d59/32.png) [@Simon\_Pichugin](https://forum.ansible.com/u/Simon_Pichugin)\
**Post date:** [May 6, 2022, 4:24am UTC](https://forum.ansible.com/t/389-directory-server-ansible-collection-question/36600/1 "2022-05-06T04:24:55Z")

</div>

Hi folks,

I work in Red Hat in the 389 Directory Server team (LDAP server, [https://www.port389.org/](https://www.port389.org/)).  
We are developing a 389 Directory Server Ansible Galaxy Collection for Fedora.  
The code draft we have now: [https://github.com/389ds/ansible-ds](https://github.com/389ds/ansible-ds)

For now, we’re in the **very early** development stages, so we’re still defining the overall architecture.  
I read Ansible documentation, but one thing is not 100% clear to me.

Is it the right thing to do during ansible-playbook execution?

1. Create a ‘dummy’ LDAP instance on the managed node;
2. Compare configuration between the ‘dummy’ instance and the customer’s LDAP instance;
3. Remove the ‘dummy’ instance from the managed node;
4. Proceed with the gathered data.

Will it violate any Ansible paradigms? Or it is an acceptable thing to do in the module/collection that we will ship to our users.

Thank you!  
Kind Regards,  
Simon