luxolus/open-vault
2
0
Fork 0
Code Issues 1 Pull requests Releases Activity

Fix links to documentation. (#9570)

Browse source 
* Fix links to documentation.
* Add 1.5.0 upgrade nodes to navigation.
This commit is contained in:
Mark Gritter 2020-07-22 15:55:41 -05:00 committed by GitHub
parent 645e8b6521
commit 5fc28fe65a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
website/data/docs-navigation.js
View file

@ -384,6 +384,7 @@ export default [
'upgrade-to-1.3.5',
'upgrade-to-1.4.0',
'upgrade-to-1.4.1',
'upgrade-to-1.5.0',
],
},
'----------------',

6
website/pages/docs/upgrading/upgrade-to-1.5.0.mdx
View file

@ -23,14 +23,14 @@ configuration is 1MiB.
In addition, a new metric has been introduced, `vault.raft-storage.entry_size`,
that allows for operators to sample the entry size, view the average, and adjust
the configuration value as necessary. For additional details, please see
[Raft configuration](docs/configuration/storage/raft).
[Raft configuration](/docs/configuration/storage/raft).
## Known Issues
### Enabling telemetry on 32-bit systems will cause Vault to crash.
A workaround for this issue is to disable collection of usage gauges in
the [telemetry](docs/configuration/telemetry) stanza of the configuration.
the [telemetry](/docs/configuration/telemetry) stanza of the configuration.
```
telemetry {
@ -46,7 +46,7 @@ that were introduced in version 1.5.0, but all other Vault telemetry will remain
### Non-string values in seal config prevent startup
Any values in the [Seal configuration stanza](https://www.vaultproject.io/docs/configuration/seal)
Any values in the [Seal configuration stanza](/docs/configuration/seal)
that are not quoted strings yield a parse error of the form:
```