No more DSLs for deployment/config management tasks please. Too many already.
Bashible: An Ansible-inspired deployment/automation tool written in Bash DSL
11–20 of 86 posts
Re: Bashible: An Ansible-inspired deployment/automation tool written in Bash DSL
#12Re: Bashible: An Ansible-inspired deployment/automation tool written in Bash DSL
#13Portability is pretty important in the deployment/automation space and it's hard to beat bash in that capacity. It just sucks that bash sucks so much.
Re: Bashible: An Ansible-inspired deployment/automation tool written in Bash DSL
#14Re: Bashible: An Ansible-inspired deployment/automation tool written in Bash DSL
#15Re: Bashible: An Ansible-inspired deployment/automation tool written in Bash DSL
#16I’m surprised there’s no explanation of why Bash was chosen for this.
I'd imagine it's because it's available everywhere (even openwrt routers and those things), and it's easier to get away with not having to use sudo (depending on the task you are doing, of course). With Ansible, you almost always need python installed on the target host. Which, in 95% of cases is not a problem. It's not ideal to install a system package just because you want to do some provisioning (there are ways ar…
BASH itself? Or a Bourne-family shell? I thought most embedded systems were shipping busybox's ash as /bin/sh
Re: Bashible: An Ansible-inspired deployment/automation tool written in Bash DSL
#17Earlier quoted context omitted.
> complex logic encoded into YAML This should stop too.
What's the answer then?
Except...
When we find a new problem, we solve it the way we always solve things. And we like to solve things with tons of impenetrable abstraction. We hardly care about legibility of stack traces let alone ease of tracing through the code.
I'm sure 24-year-old me would disagree with this, but I think there's a qualitative difference between an arcane abstraction for getting text onto a scroll area on a screen and arcane abstraction that lets me accidentally undeploy all of my servers (24 year old me would be equally frustrated by both).
BDD test frameworks mostly look like imperative code, and after the initial shock of learning that some things are declared/registered immediately and executed only after everything else has gotten a chance to register, it's not that difficult to figure out how things work (until you have to step into the internals, and some test frameworks are okay, while others are a disaster).
I kinda think infrastructure as code should just be code. Give me something that looks like a test framework but with better adherence to Least Surprise.
Re: Bashible: An Ansible-inspired deployment/automation tool written in Bash DSL
#18No more DSLs for deployment/config management tasks please. Too many already.
I'd rather more DSLs than more things with complex logic encoded into YAML.
Re: Bashible: An Ansible-inspired deployment/automation tool written in Bash DSL
#19Are there any other Ansible alternatives that avoid the whole YAML mess?
Maybe what we need is a set of CLI commands that mirror Ansible modules in performing idempotent operations through SSH and APIs.
Re: Bashible: An Ansible-inspired deployment/automation tool written in Bash DSL
#20Earlier quoted context omitted.
I'd rather more DSLs than more things with complex logic encoded into YAML.
I'd argue that Ansible is using a DSL, just one that happens to be expressed in YAML. I mean, it has loops, conditionals, various forms of subroutines (roles, plays that can be included)... I don't think that using a YAML format rather than being C-shaped makes it any less a DSL.