Ansible

“My ansible playbook customizes so much already it wouldn't take too much more to just start from debian tbh.”

“Ansible to configure live machines.”

“information about ansible runs across our fleet”

“AI tools managing our services using ansible/terraform”

“I use a lot of ansible for several of our deployments. At this point, most of that is managed via codex.”

“Some of our ansible integration tests would be 5 - 10 cents - and we run like 50 - 100 of those per day.”

“Claude reviewed our current Ansible code base and already highlighted a few errors”

“One being Ansible and other being network segmentation.”

“Eventually we moved to Ansible and I sold that business”

“deployed to VMs with ansible, so manual work to write the upgradeprocessfor me”

“I've been using #!/usr/bin/env -S ansible-playbook --diff to turn ansible playbooks to scripts”

“why bother testing that ansible can write a variable into a file if the template is changed”

“If you tried using ansible once a month without our host key certificates, you'd have ansible barf about a dozen unknown host keys”

“or your ansible setup and reinstall it all.”

“I've done EC2 auto-scaling with ansible and packer”

“everything is glued together / configured / deployed via ansible.”

“I've included it in my ansible setup, so the basis, distro, os updates, firewalls, backups are cositent with my other servers.”

“I've had similarly complicated problems with Terraform, Ansible, Chef and Puppet and just plain Linux as I have had with Kubernetes.”

“I maintain a fork of Ansible that has niceties like blocks you can loop over.”

“before I formalized in an ansible script”

“I tweak a number in Terraform templates and manually run the ansible playbook for each new server.”

“I then lead another whole project to migrate the whole company to Git and Ansible for deploys.”

“configuration management? ansible / salt”

“the deploy is invoked by ansible, whose own expect module recommends the real expect”

“We use ansible-pull to decentralize our Ansible runs as much as possible, but we also use Hashicorp Vault's SSH Key Certificates functionality”

“we use a mix of ansible tower (which I don't love) and ansible runs from local machines”

“We've been using AWX (and Ansible Tower) for orchestrating our Ansible deployments and playbooks for a while now.”

“This is scaringly close to how we run geocod.io - right down to the ansible provisioning wrapper that I put together”

“the App team decided to go with Ansible while Unix Ops stuck with Puppet.”

“I learned and brought in production the followings: Ansible and Terraform”

“I just use the same chef, puppet or ansible playbook I will use for a physical server”

“At the moment we use Ansible but it runs over WinRM which is completely unreliable”

“tons of terminal usage, Ansible, VMs, etc..”

“We build on a continuous integration server and deploy using Ansible or AWS CodeDeploy.”

“We migrated from Debian+Ansible to NixOS to easier be able to ensure consistency across servers.”

“You can build all of what I mentioned with OSS like: Ansible (deployment) Jenkins (ci) ELK stack (metrics / logging) Zabbix (system metrics)”

“it wants our Vault password to load the inventory, and the inventory task doesn't allow for associating vault credentials.”

“I can provision my machine using the ansible scripts we use to provision our production machines”

“in this particular course we use Ansible to verify students' solutions.”

“ansible worked on them precisely once after initial install and then never again”

“I'm not much of a sysadmin guy (developer-turned-Ansibleman)”

“laid over some existing provisioning system like salt, ansible (or just a whole shit ton of puppet work)”

“the Ansible playbook we use to launch the docker containers”

“which is easy to manage with docker-compose, Ansible, etc.”

“We use multiple cloud providers (Digital Ocean and AWS being our primary), Play Framework, AKKA , Ansible for deployment, Shippable for our CI”

“a whole bunch of ansible scripts to setup checks for postgres, nginx, etc.”

“This is not stuff that great UX with Ansible will fix”

“we've started experimenting with Ansible to perform simple setup of hosts”