-
Not sure if I am doing something wrong - but using the exact playbook from the documentation (and having installed the collection earlier) I get
And my playbook is:
I did see in the main readme it talks about coturn being a dependency, but I don't need anything else done, really - just this |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
The "coturn" role is part of the next release of the collection, and is not available yet on Ansible Galaxy. It is the reason why the error say that the role is "not found". You may pull the collection using git to get the current main branch. I do no plan to change the "coturn" role until the release, so it is safe to do so. Even if this particular role is flagged as "dependency", you can use it safely as it. It does not depends on others. |
Beta Was this translation helpful? Give feedback.
-
awesome, thanks |
Beta Was this translation helpful? Give feedback.
The "coturn" role is part of the next release of the collection, and is not available yet on Ansible Galaxy. It is the reason why the error say that the role is "not found".
You may pull the collection using git to get the current main branch. I do no plan to change the "coturn" role until the release, so it is safe to do so.
Even if this particular role is flagged as "dependency", you can use it safely as it. It does not depends on others.