-
Notifications
You must be signed in to change notification settings - Fork 229
Open
Description
If I add an unknown keyring-backend value of local it is not possible to replace it with a valid one test without still encountering the error that was produced from adding the wrong one
(base) root@localhost:~# secretcli config set client keyring-backend local
Error: couldn't get keyring: local: unknown keyring backend [scrtlabs/cosmos-sdk@v0.50.10-secret.2/crypto/keyring/errors.go:13]
(base) root@localhost:~# secretcli query bank balances secret1u9jfestafdkr5cr057e436puzp6agf2vvcejfc | jq
Error: couldn't get keyring: local: unknown keyring backend [scrtlabs/cosmos-sdk@v0.50.10-secret.2/crypto/keyring/errors.go:13]
(base) root@localhost:~# secretcli config set client keyring-backend test
Error: couldn't get keyring: local: unknown keyring backend [scrtlabs/cosmos-sdk@v0.50.10-secret.2/crypto/keyring/errors.go:13]
It was only possible to find out by inspecting secretcli config --help that showed secretcli config home was located at /root/.secretd, so I manually edited vim /root/.secretd/config/client.toml changing the value back to test
# The keyring's backend, where the keys are stored (os|file|kwallet|pass|test|memory)
keyring-backend = "test"
Metadata
Metadata
Assignees
Labels
No labels