Re: [ansible-project] Automatically connecting as different user on later runs after 'root' is disabled

Thanks for the thoughts Brian. > You could have the first task attempt to 'connect as root and set > the other user', ignore their failure and continue with rest of > play with correct credentials This is a new idea to me. Obviously some smell around ignoring failures. > You could skip the 'a

[ansible-project] Automatically connecting as different user on later runs after 'root' is disabled

Hi, One of my tasks disables root over ssh. Another creates an 'app' user that has sudo powers. That means that the way to connect to the host changes after the first run. Is there a smarter way to easily adjust to this new state than manually adding --become and --user command-line options to

[ansible-project] Can I convince anybody that the mysql_db state=import behavior is a bug?

Hi, As discussed at here a long time ago ,mysql_db state=import will import the given file unconditionally. There's a good chance the database has been updated since the original run of ansible, so this behavior m

[ansible-project] Re: Shell Permission denied

My OCD is noticing that Ansible's running --list, but you use -l from the command line. Of course no difference, right? I don't know what the problem is, but maybe it's not becoming root? Can you shell:whoami? -- You received this message because you are subscribed to the Google Groups "Ans

[ansible-project] Re: Specfic multistage application deployment methodology

I'm not understanding your problem, and am too new to help anyway, but I'll ask a clarifying question: Are you hoping Ansible sets up your development environment, or that it accesses it during deployment? -- You received this message because you are subscribed to the Google Groups "Ansible P