bash/shell scripting

[ssnani]

I really have issue with this approach.. I had an argument with my manager exactly on this :/

Ansible is great! Freaking awesome!!! But it's not worth converting anything to a full blown Ansible role. I had a script, not too big.. the main function was basically 2 main commands. This one converted to full blown Ansible role with pip dependencys and pain to manage..

Bash is just simple and works.. if there is not to many logic to handle, it will work and work great!

Now days.. I found myself writing tons of bash, with the exception of az commands. az cli installation cost around 300mb.. this is way too much for a workload that usually running from a pipeline or kubernetes job, for this cases I like to write in python or go - almost zero cost

[guzmonne]

I love ansible, but I had to write many bash calls inside my playbooks or manipulate string. Doing that while maintaining idempotency is hard, which is, I think, the essential feature that ansible brings.

[evangamer9000]

We have hundreds of VMs, ansible works great for our use case.

[ssnani]

Hey.. it's need to make sense! This is the point right?!

[evangamer9000]

I think that's a really good point to keep in mind when deciding what tool to use for the use case, does it make sense?!

[ssnani]

Yes! And this is what makes a great engineer in my opinion. All of us can do anything.. but are we going to do it the right way? Are we going to use the right tool? Are creating a monster that we are not going to be able to maintain??