Timeline for How is Ansible different from simply running a provisioning bash shell in Vagrant?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 7, 2017 at 0:44 | comment | added | Michaël Le Barbier | I also subscribe to your answer, especially having put the available experience in the balance. I have two small critics: first is the idempotency This is of course an important aspect of configuration systems, but since it is possible to use any possible shell commands in ansible playbooks, the system can at best incitate to use idempotency. (We actually want something more powerful that idempotency aba = ab.) Second the reliable management of remote execution might be totally irrelevant in some important cases, e.g. when implementing the immutable server pattern using instance images. | |
| Mar 5, 2017 at 20:58 | comment | added | ᴳᵁᴵᴰᴼ | Liked your answer; I would also mention that, if the bash team is going for idempotency, execution management, and reuse, basically writing their own config management framework, there is a cost involved, and we all know that is can get really nasty for in-house projects. | |
| Mar 5, 2017 at 13:52 | history | answered | Assaf Lavie | CC BY-SA 3.0 |