Thanks Dick,
'policy scar tissue' :')
Thats great, I am going to use that. It's more that we have had no CM, it
all been manual in the past. Have tried to say by implementing Ansible we
do no need the complete separation, so will have to prove it. The agentless
of ansible was the key point for
We run the same playbooks against 7 (!) various staging environments,
with a different inventory
for each. Per-environment config goes into the inventory under the
[all:vars] key - including things
like versions of RPMs etc.
SSH credentials are managed out of band, but there's a central git
repo
Hey Byron,
I'm using Ansible with multiple environments daily and it's very easy
once you unlearn what Ansible documentation presents as a best
practice. :-)
First, forget about /etc/ansible/ directory and its contents. Instead,
in your home directory create separate directories, each one for a
HI All,
First post and we are looking to implement Ansible into a new cloud
environment for multiple legacy systems.
Sorry but there is a bit of a story first and this is more a
setup/component architecture question as we have a security constraint that
production and non-production data
