4 ms·
I have used Ansible for some years. I recently switched jobs to a company having no automation on VMs. And we are migrating our workload to managed services in
by whirlwin 5y ago
I have used Ansible for some years. I recently switched jobs to a company having no automation on VMs. And we are migrating our workload to managed services in the cloud (managed Kubernetes), I have to say I'm relieved I don't have to deal with Ansible again. It's probably very efficient in many ways, but just copying a file/directory with the correct options is a bit of pain in Ansible. Having not to worry about VMs anymore is a huge win for me at least. /OffTopicEnd
- yjftsjthsd-h 5y ago> just copying a file/directory with the correct options is a bit of pain in Ansible. How so? Do you mean you had trouble remembering what arguments to pass to the copy module? (I'm not sure what other options there are to be a pain)
- justin_oaks 5y agoI'm not the one you're replying to, but I one problem I've had with Ansible directory copying is that it's terribly slow. Using the "state" parameter for files and directories is also rather odd. You specify "state: absent" to delete, "state: directory" to create a directory. It makes sense considering the declarative nature of Ansible, but it's unfamiliar to those used to writing shell scripts.
- yjftsjthsd-h 5y agoYes, ansible in general is painfully slow; I guess I assumed "painful" meant hard to write