Tape Vault, five months on

I started building Tape Vault in June. I wanted a way to see what had changed on a Tape record and recover an earlier value when something went wrong. By summer I had a working system that could connect to Tape apps and keep a history of their changes. I was using it, and there were a few bugs and rough edges to work through.

The 10 November update was the biggest pass I’ve made on those rough edges. I spent most of it on what happens before you get to the history: connecting an organisation, signing in and getting to the right organisation if you use more than one.

Getting set up and signed in

I made organisation setup resumable, so if you stop partway through connecting Tape, you can pick it up again. I also worked through some sign-in and session issues and made it easier to get to the right organisation from the same account. I tested the updated flow with three Tape organisations and successfully restored a change to a record.

Keeping up with Tape’s API

Tape had also changed parts of its API since I started the project. The most visible change for anyone setting up Tape Vault is support for personal access tokens, or PATs. The setup now accepts a PAT and explains which permissions it needs. I also updated how Tape Vault verifies webhooks, the notifications it uses to pick up changes in Tape.

I’ve written up the November update for testers, including what changed for people already using Tape Vault and where to start if you’re connecting an organisation for the first time.