a3dfde5cec
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
60 lines
2.7 KiB
Markdown
60 lines
2.7 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Upgrading to Vault 0.9.2 - Guides"
|
|
sidebar_title: "Upgrade to 0.9.2"
|
|
sidebar_current: "docs-upgrading-to-0.9.2"
|
|
description: |-
|
|
This page contains the list of deprecations and important or breaking changes
|
|
for Vault 0.9.2. Please read it carefully.
|
|
---
|
|
|
|
# Overview
|
|
|
|
This page contains the list of deprecations and important or breaking changes
|
|
for Vault 0.9.2 compared to 0.9.1. Please read it carefully.
|
|
|
|
### Backwards Compatible CLI Changes
|
|
|
|
This upgrade guide is typically reserved for breaking changes, however it
|
|
is worth calling out that the CLI interface to Vault has been completely
|
|
revamped while maintaining backwards compatibility. This could lead to
|
|
potential confusion while browsing the latest version of the Vault
|
|
documentation on vaultproject.io.
|
|
|
|
All previous CLI commands should continue to work and are backwards
|
|
compatible in almost all cases.
|
|
|
|
Documentation for previous versions of Vault can be accessed using
|
|
the GitHub interface by browsing tags (eg [0.9.1 website tree](https://github.com/hashicorp/vault/tree/v0.9.1/website)) or by
|
|
[building the Vault website locally](https://github.com/hashicorp/vault/tree/v0.9.1/website#running-the-site-locally).
|
|
|
|
### `sys/health` DR Secondary Reporting
|
|
|
|
The `replication_dr_secondary` bool returned by `sys/health` could be
|
|
misleading since it would be `false` both when a cluster was not a DR secondary
|
|
but also when the node is a standby in the cluster and has not yet fully
|
|
received state from the active node. This could cause health checks on LBs to
|
|
decide that the node was acceptable for traffic even though DR secondaries
|
|
cannot handle normal Vault traffic. (In other words, the bool could only convey
|
|
"yes" or "no" but not "not sure yet".) This has been replaced by
|
|
`replication_dr_mode` and `replication_perf_mode` which are string values that
|
|
convey the current state of the node; a value of `disabled` indicates that
|
|
replication is disabled or the state is still being discovered. As a result, an
|
|
LB check can positively verify that the node is both not `disabled` and is not
|
|
a DR secondary, and avoid sending traffic to it if either is true.
|
|
|
|
|
|
### PKI Secret Backend Roles Parameter Types
|
|
|
|
For `ou` and `organization` in role definitions in the PKI secret backend,
|
|
input can now be a comma-separated string or an array of strings. Reading a
|
|
role will now return arrays for these parameters.
|
|
|
|
|
|
### Plugin API Changes
|
|
|
|
The plugin API has been updated to utilize golang's context.Context package.
|
|
Many function signatures now accept a context object as the first parameter.
|
|
Existing plugins will need to pull in the latest Vault code and update their
|
|
function signatures to begin using context and the new gRPC transport.
|