gardar
gardar
> Thanks @gardar - you bring up interesting points. Can you open a [forum topic](https://forum.ansible.com/c/project/7) on this so it gets wider community discussion, and then add the link to that...
Traced this down to the initial commit for the collection structure docs https://github.com/ansible/ansible-documentation/commit/49983fdaf78c3ac286f6155e4eb91d5cb0e2af8f, but I don't see any reasoning behind it. Perhaps this was an issue with the old galaxy...
So... Where do we stand with this now? Are there any obstacles for getting this fixed in the docs?
Perhaps you already have controlpersist in your ssh config?
Do you by any chance have facts gathering disabled?
That's most likely the issue then, the roles all rely on Ansible facts to some degree.
> Is that documented somewhere? Cuz that wasn't clear to me as a pre-req. Yes and no, perhaps not clearly enough. You can see in the docs that some of...
It is out of scope for the roles but it's pretty simple to do by adding a task in your playbook to create the user there, then when the role...
> I noticed two things: > > 1. When trying to update the value for a variable that doesn't have an override value, we get an error. We should catch...
I'm afraid I made some conflicting changes in #507 but I had this change in mind and moved the localhost delegation to the block level