It's great for one liners, but it breaks down when doing simple things like checking if a variable is a string or integer.

    set -euo pipefail

    set -o errexit
    set -o nounset
    set -o pipefail

    set +o errexit

    ansible-playbook ...

    if [[ "$?" != "0" ]]; then
        echo -e "\e[1;31m""Error when executing ansible!""\e[0m"
        exit 1
    fi

    set -o errexit

    # the :- operator means "use the right side value if the left side ($1) is not set"
    env=${1:-}
    
    inventoryFile="${baseDir}/env/${env}/inventory"

    if [[ -f "${inventoryFile}" ]]; then
        echo -e "\e[1;31m""Invalid environment specified!""\e[0m"
        exit 1
    fi

    if ! ansible-playbook ... ; then 
        echo -e "\e[1;31m""Error when executing ansible!""\e[0m"
        exit 1
    fi

-e Abort at the first failed line

-u Abort when undefined variable is used

-o pipefail Piped commands return the status of the last failed command, rather than the status of the last command

Does all the same with more commands and better error handling.

Odd. I see almost entirely Ruby. Especially with tools like Chef.