Implementations across cloud providers are going to be different, and I don't know how AWS vs GCP vs Azure is handling failure, so now it's your responsibility.
Now the problem has grown from just write a few lines of bash script to, "create a script that can handle failure and reverts it so a known state", this is a more complex problem than just creating a resource. And now multiply this for all different resources, EC2, AKS, RDS, Security Groups ... and keep up with the API.
And if somebody joins your team, and wants to contribute to the solutions, they're going to have to understand the codebase.
To get data in Terraform you have outputs and you can display the data.
Terraform helps you to have a unified way to manage your resources, sure the bash scripts works for you, but what happens if you leave the company? Somebody else has to maintain your shell script.
What happens if somebody else is changing the infrastructure and they're not familiar with your shell script, they need time to dig in to figure things out and then update it, and in best case test it.
And you need to keep your scripts up to date, you need to build in fault tolerance, you need to think how you're going to deploy new resources. How are you going to handle destroying resources?
And on top of that you also need to learn the cloud Provider CLI tools or API to know what kind of calls to execute.
It just provides a standardised way to manage your infra.
Can you elaborate more on the TTS? Did you prerecord fragments (how many did you actually do?) and you just stich them together? So there is a may.mp3, 22.mp3 and your scripts just puts them together?
As a Solutions Engineer I've talked with a lot of companies, we're selling software to enterprises. A lot of prospects take Gartner as a starting point and evaluate multiple solutions from there.
Now the problem has grown from just write a few lines of bash script to, "create a script that can handle failure and reverts it so a known state", this is a more complex problem than just creating a resource. And now multiply this for all different resources, EC2, AKS, RDS, Security Groups ... and keep up with the API.
And if somebody joins your team, and wants to contribute to the solutions, they're going to have to understand the codebase.