ENOSUCHBLOG

Programming, philosophy, pedaling.

KBSecret 1.3.x

Apr 4, 2018     Tags: devblog, kbsecret, programming, ruby    

This post is at least a year old.

The KBSecret 1.3.x tree has just been released, after five prereleases.

This post will quickly summarize some of the important changes between the 1.2.x and 1.3.x versions.

“In-process” commands

All of the commands included by a default KBSecret installation now run in just one process, providing a substantial performance boost.

The original flow for executing KBSecret commands looked (roughly) like this:

  1. The user calls kbsecret list
  2. The kbsecret command translates list to kbsecret-list
  3. kbsecret-list is execed

As a result, every kbsecret command invocation (pointlessly) required the Ruby runtime and all dependencies to be loaded twice.

As of 1.3.x, the flow for executing kbsecret list looks (roughly) like this:

  1. The user calls kbsecret list
  2. The kbsecret command calls KBSecret::CLI::Command.run! with "list"
  3. KBSecret::CLI::Command.run! translates list to KBSecret::CLI::Command::List and calls run! on a new instance of it

This only requires Ruby and all of the KBSecret dependencies to be loaded once. In local testing, this speeds up most invocations by around 40%.

As part of this change, KBSecret no longer distinguishes between “built-in” (meaning baked into the kbsecret script itself) and “internal” commands — all commands included with KBSecret are now “internal.”

New flags for kbsecret commands

kbsecret commands now supports the -i, --internal-only and -e, --external-only flags for filtering output by command type:

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

$ kbsecret commands -i
stash-file
raw-edit
sessions
new
todo
pass
conf
cp
env
help
dump-fields
login
commands
types
list
generators
generator
version
rm
session

$ kbsecret commands -e
yad-login
dmenu-pass
recovery
audit-pass
todo-list
snip
discover-sessions

As before, running kbsecret commands without any flags prints all commands, internal and external.

Command aliases

KBSecret now supports adding aliases for commands via the commands.ini file. Aliases are declared via an aliases key under each command’s section, and are space-separated:

1
2

[list]
aliases = l ls print-all-my-records

As a result, all of these invocations do the same thing:

1
2
3
4

$ kbsecret list
$ kbsecret l
$ kbsecret ls
$ kbsecret print-all-my-records

The commands.ini file can be opened in your $EDITOR by running kbsecret conf -c.

Integrated command unit tests and test coverage

As of 1.3.1, KBSecret’s library and CLI unit tests have been integrated: make test now runs both via the same rake task, rather than splitting them across multiple tasks. This has allowed for the integration of coverage results into the CLI tests (which are currently at 96% coverage!)

I wrote an entire separate blog post on integrating code coverage into KBSecret’s CLI tests, which you can find here. You might find it interesting if you’ve struggled with coverage reports across multiple processes.

Summary

As always, check KBSecret’s website for the latest documentation (and references to the API docs).

Thanks for reading!

Discussions: Reddit