I had the same issue on Centos, i.e. I added a script and nothing happened. Not tried on Debian based distros, but I found building a base AMI with cloud-init installed and, in /etc/cloud/cloud.cfg set 'disable_root: false', solved it for me. Then launch an instance of that base AMI, setting the user-data. In my case it wasn't an ansible issue, but a limitation of the AMI I chose.
-- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/ed829261-5858-4457-b6f3-01ce4d2566e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
