Thank you Matt, adding FQDN of the module fixed the problem either in
playbook or ansible-doc command line.

How is that existing modules can be found just with their name but not the
new one ?
There is action_groups.yml in meta directory, but adding testing_module to
it didn't make any difference.

On Mon, 8 Jun 2020 at 10:00, Matt Martz <[email protected]> wrote:

> You have to use the FQCN of the module, at least for ansible-doc:
>  community.aws.testing_module
>
> On Mon, Jun 8, 2020 at 9:58 AM Sydo Luciani <[email protected]>
> wrote:
>
>> Created a new module in
>> "~/ansible_dev/ansible_collections/community/aws/plugins/modules", but
>> neither ansible-playbook nor ansible-doc finds the new module. for the sake
>> of test, copied a module to new name, to make sure it is not related to
>> module content, and original module can be found, but not the new one.
>>
>> ansible-doc -t module testing_module
>>
>> Checking collections development document:
>>
>> https://docs.ansible.com/ansible/latest/dev_guide/developing_collections.html
>>
>> but can't find any thing about adding a new module.
>>
>> What am I missing ?
>>
>> Thanks
>>
>>
>> On Thu, 4 Jun 2020 at 22:10, Jordan Borean <[email protected]> wrote:
>>
>>> You've identified one of the many annoying parts of collections. You
>>>> need a special directory structure and you can't install from git in an
>>>> editable manner.
>>>
>>>
>>> Admittedly you are right about the special directory structure but it's
>>> pretty trivial to install it from git in an editable manner. I do this for
>>> the Windows collections;
>>>
>>> # Usually I have this in my ~/.bashrc where the last segment is my dev
>>> location
>>> export ANSIBLE_COLLECTIONS_PATHS=~/.ansible/collections:/usr/share/
>>> ansible/collections:~/ansible-dev
>>> git clone [email protected]:ansible-collections/ansible.windows.git ~
>>> /ansible-dev/ansible_collections/ansible/windows
>>>
>>> I won't lie and say this is a perfect scenario but it's just 2 commands,
>>> one of which can be set automatically in your profile.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Ansible Project" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/ansible-project/c3c6a188-ff2c-4d5c-be96-774ce225023fo%40googlegroups.com
>>> <https://groups.google.com/d/msgid/ansible-project/c3c6a188-ff2c-4d5c-be96-774ce225023fo%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Ansible Project" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ansible-project/CAJspodimWwD2Tgo4Go5dPXVepjnTiEuU7T3ooO8LRAwU2Vm6Eg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/ansible-project/CAJspodimWwD2Tgo4Go5dPXVepjnTiEuU7T3ooO8LRAwU2Vm6Eg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> --
> Matt Martz
> @sivel
> sivel.net
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/CAD8N0v_-rEDhjHZkK40VZk3XQ0eZEaB__L%3DARkqag%3DAe7dd7jg%40mail.gmail.com
> <https://groups.google.com/d/msgid/ansible-project/CAD8N0v_-rEDhjHZkK40VZk3XQ0eZEaB__L%3DARkqag%3DAe7dd7jg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAJspodghPuEcjBTjN-o%2BSD3ZU-bigDJwEG85FNnv8-tw8MfUBw%40mail.gmail.com.

Reply via email to