Thank you Jordan. On Tue, Jul 30, 2019, 6:58 PM Jordan Borean <jborea...@gmail.com> wrote:
> There are multiple ways you can get around this, you could; > > - Store the password in a vault file so the user would need to know > the vault key when running your playbook > - Use a lookup plugin to lookup the password during runtime > - Don't use a password at all, kerberos can use the existing ticket > checked out with kinit before running the playbook > > You shouldn't have your password in plaintext at all, most of the time the > docs only have it there just for documentation purposes. > > Thanks > > Jordan > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/b92f6b8b-d108-4a47-a911-ca21ce05f348%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/b92f6b8b-d108-4a47-a911-ca21ce05f348%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 ansible-project+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAP10WQe-UifoTrn%2Bbmn6EfTqU5YYhbw%3D%3DP5-AQ3NZ3f_3FhK_g%40mail.gmail.com.
