1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
---
date: 2024-04-02
title: Bashtard v2.1.0
tags:
- Bash
- Bashtard
- FreeBSD
- GNU+Linux
---
Its been about another year since I made a post about Bashtard, its [2.0.0
release](https://www.tyil.nl/post/2023/05/23/bashtard-v2.0.0/). Today marks the
[2.1.0 release](https://www.tyil.nl/projects/bashtard/releases/2.1.0), meaning
I've gone almost a year without breaking backwards compatibility. To me, this is
a very good sign.
The release today isn't as big as the 2.0.0 release was, mostly because most
of the functionality I want to have is already present. Some new features were
added over the year, though. The most important one is _variable references_.
This allows re-use of a variable's value for another variable. Its quite
simplistic in how it works, due to the nature of Bashtard being written in Bash
and trying to keep things rather simple and lightweight. It does however get the
job done for most use-cases I had for it.
Another feature that was added in this release is the `zap` subcommand. It is a
convenience command more than anything, simply removing an existing registry
entry without going through `playbook_del()`. The use case for this is mostly
for testing new playbooks. I found that while writing a playbook I'd often
remove the playbook entry from the registry to re-run the `playbook_add()`
function to see if it works exactly as desired, and I wanted this to be more
convenient. In theory this new `zap` subcommand is also useful for dealing with
entries of broken or removed playbooks.
For a future release I'd like to add `import` and `export` subcommands, for
making it easier to handle external playbooks. The `import` subcommand is
intended to take an URL and optionally a name to simply add an existing
repository as a submodule in the `playbooks.d` directory.
The `export` subcommand should take a name as it exists in the `playbooks.d`
directory and turn it _into_ a git submodule, so it can be pushed to its own
repository. The intent is that you can just make a regular playbook for use
within Bashtard, and if you decide "hey, this could actually be useful for
others in its current state", you can simply export it, and push it to a
repository for other people to pull from.
Additionally, I would like to remove the `backup` subcommand from Bashtard, as I
feel it adds a level of bloat and scope-creep which simply should not be there.
While this would result in a 3.0.0 release of Bashtard, keeping it just for
backwards compatibility seems a little silly to me.
I'm on the fence for the `ssh` subcommand, as it seems more closely aligned to
Bashtard being used to manage several systems, and ssh can be very useful to
check something across your entire network. Considering the recent [SSHd
vulnerability](https://www.cve.org/CVERecord?id=CVE-2024-3094), it was quite
easy to run a single command across all my machines and get an overview of which
machines were affected.
Let's see what the rest of this year brings in Bashtard changes!
|
