docs/setup: contract "cannot" in the KV-mount troubleshooting block
The `prose lint (vale, errors)` CI gate fails on Microsoft.Contractions at `setup.md:147`, in prose this branch adds. Verified against the repo's own styles rather than assumed: with `XDG_DATA_HOME=$PWD/.vale-data vale sync` (the ini's own note — sync ignores `StylesPath` and writes under `$XDG_DATA_HOME`), the file reports 0 errors, and a copy of it with the word put back reports that line and nothing else. Without the sync, vale exits 2 on a missing styles dir, which is a config error rather than a pass.
This commit is contained in:
parent
48e6a0b88f
commit
b0edb5b2cc
1 changed files with 3 additions and 3 deletions
|
|
@ -144,9 +144,9 @@ forgotten one expires rather than lingering.
|
||||||
|
|
||||||
A store bootstrapped by an earlier version has the policy, the auth method and
|
A store bootstrapped by an earlier version has the policy, the auth method and
|
||||||
the role, but no `secret/` engine — the controller's first credential write
|
the role, but no `secret/` engine — the controller's first credential write
|
||||||
answers `no handler for route "secret/data/…"`. The bootstrap token cannot fix
|
answers `no handler for route "secret/data/…"`. The bootstrap token can't fix it
|
||||||
it either: the policy it was minted from names nothing under `sys/mounts`. Mount
|
either: the policy it was minted from names nothing under `sys/mounts`. Mount it
|
||||||
it once with the root token from `init`:
|
once with the root token from `init`:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
sudo bash -c 'BAO_TOKEN="<root token>" bao secrets enable -path=secret kv-v2'
|
sudo bash -c 'BAO_TOKEN="<root token>" bao secrets enable -path=secret kv-v2'
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue