This is a simple Spin component for exploring the contents of key/value stores.
First, configure the template:
$ spin templates install --git https://github.com/fermyon/spin-kv-explorer
Copying remote template source
Installing template kv-explorer...
Installed 1 template(s)
+------------------------------------------------------+
| Name Description |
+======================================================+
| kv-explorer Explore the contents of Spin KV stores |
+------------------------------------------------------+Then, you can either create a new application, or add this component to your existing app:
$ spin new kv-explorer
# OR
$ spin add kv-explorerThis will create the following component in your spin.toml:
[[component]]
source = { url = "https://github.com/fermyon/spin-kv-explorer/releases/download/<latest-release>/spin-kv-explorer.wasm", digest = "sha256:aaa" }
id = "kv-explorer"
# add or remove stores you want to explore here
key_value_stores = ["default"]
[component.trigger]
route = "/internal/kv-explorer/..."You can now access the explorer in your browser at the route /internal/kv-explorer.
When running locally, you can skip checking for the crendentials on every request by passing the SPIN_APP_KV_SKIP_AUTH environment variable:
$ spin up --env SPIN_APP_KV_SKIP_AUTH=1When deploying to Fermyon Cloud, you can pass the credentials pair together with the spin deploy command:
# change the value to your desired basic authentication credentials
$ export KV_CREDENTIALS="user:password"
$ spin deploy --key-value kv-credentials=$KV_CREDENTIALSThe explorer will use the default store to persist the credentials to access the UI and the API. If no values are set, the first invocation will set a randomly generated pair of username and password under the kv-credentials key, with the value following the user:password format. On the first run, the values will be printed in the logs, and they can be used to log in and change them (creating a new credentials value will override the existing value).
- the explorer can only be used with Spin's default key/value store. When this will be configurable, this component will support working with custom stores as well.