Multiple values for ansible connection properties

Has anyone heard of providing a second --user/–privatekey to ansible-playbook command, just in case the first user/privkey authentication fails?

Seem to remember something about this in an Ansible session on the RHEl summit last year.

regards,
Ivan.

some background on why I could use this is: configuring systems pre-deployed on different cloud providers, on one if need to start with ‘root’ to create the ansible user, on the other i dont have root, but it’s ‘localadmin’)

Now i have build a script around ansible-playbook, to determine on which provides i will be deploying.
If i could pass both, i would not need this script construction. From ansible perspecitiv, i should not need to care, where my vm is residing…

ivan.

some background on why I could use this is: configuring systems pre-deployed on different cloud providers, on one if
need to start with 'root' to create the ansible user, on the other i dont have root, but it's 'localadmin')
Now i have build a script around ansible-playbook, to determine on which provides i will be deploying.
If i could pass both, i would not need this script construction. From ansible perspecitiv, i should not need to care,
where my vm is residing...

Why don't you put this information into group_vars/host_vars in your inventory?

Regards
         Racke

Thanks Racke,

yes i thought about this. This would require me to split the hosts in multiple groups (lets say: grp_VMWare, grp_MSAzure, grp_OracleCloud etc)
And that would require some more administration,

Thanks for the tip, this will keep me thinking some more about this suggestion, while waiting for other solutions.

Thanks!
Ivan.

Thank you for the response. However, I have tried with quotes, without quotes, encrypted, decrypted, hashed, unhashed, it just does not seem to work.

Rene