This is driving me a bit nuts. As far as I can tell sbx secret rm only handles service secrets. I could not find any syntax that removes a custom secret (tried the placeholder, the env name, the host). Combined with the placeholder-keyed upsert behavior (#NNN) this means a mistyped custom secret can only be cleaned up with sbx reset, which nukes all sandboxes and templates, or by editing the keychain by hand.
The workaround I ended up with was "parking": repoint the unwanted placeholder at a junk host so it becomes inert.
sbx secret set-custom -g --host unused.invalid --env PARKED_1 --placeholder "tok_oldrow00" --value parked
Works, but hopefully not the intended UX. sbx secret rm accepting the placeholder (since that is apparently the key) would do it.
Version: sbx v0.32.0 (5558036), macOS Apple silicon
This is driving me a bit nuts. As far as I can tell
sbx secret rmonly handles service secrets. I could not find any syntax that removes a custom secret (tried the placeholder, the env name, the host). Combined with the placeholder-keyed upsert behavior (#NNN) this means a mistyped custom secret can only be cleaned up withsbx reset, which nukes all sandboxes and templates, or by editing the keychain by hand.The workaround I ended up with was "parking": repoint the unwanted placeholder at a junk host so it becomes inert.
Works, but hopefully not the intended UX.
sbx secret rmaccepting the placeholder (since that is apparently the key) would do it.Version: sbx v0.32.0 (5558036), macOS Apple silicon