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
57 lines
2.2 KiB
Markdown
57 lines
2.2 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Upgrading to Vault 0.6.0 - Guides"
|
|
sidebar_title: "Upgrade to 0.6.0"
|
|
sidebar_current: "docs-upgrading-to-0.6.0"
|
|
description: |-
|
|
This page contains the list of breaking changes for Vault 0.6. Please read it
|
|
carefully.
|
|
---
|
|
|
|
# Overview
|
|
|
|
This page contains the list of breaking changes for Vault 0.6 compared to the
|
|
previous release. Please read it carefully.
|
|
|
|
## PKI Backend Does Not Issue Leases for CA Certificates
|
|
|
|
When a token expires, it revokes all leases associated with it. This means that
|
|
long-lived CA certs need correspondingly long-lived tokens, something that is
|
|
easy to forget, resulting in an unintended revocation of the CA certificate
|
|
when the token expires. To prevent this, root and intermediate CA certs no
|
|
longer have associated leases. To revoke these certificates, use the
|
|
`pki/revoke` endpoint.
|
|
|
|
CA certificates that have already been issued and acquired leases will report
|
|
to the lease manager that revocation was successful, but will not actually be
|
|
revoked and placed onto the CRL.
|
|
|
|
## The `auth/token/revoke-prefix` Endpoint Has Been Removed
|
|
|
|
As part of addressing a minor security issue, this endpoint has been removed in
|
|
favor of using `sys/revoke-prefix` for prefix-based revocation of both tokens
|
|
and secrets leases.
|
|
|
|
## Go API Uses `json.Number` For Decoding
|
|
|
|
When using the Go API, it now calls `UseNumber()` on the decoder object. As a
|
|
result, rather than always decode as a `float64`, numbers are returned as a
|
|
`json.Number`, where they can be converted, with proper error checking, to
|
|
`int64`, `float64`, or simply used as a `string` value. This fixes some display
|
|
errors where numbers were being decoded as `float64` and printed in scientific
|
|
notation.
|
|
|
|
## List Operations Return `404` On No Keys Found
|
|
|
|
Previously, list operations on an endpoint with no keys found would return an
|
|
empty response object. Now, a `404` will be returned instead.
|
|
|
|
## Consul TTL Checks Automatically Registered
|
|
|
|
If using the Consul HA storage backend, Vault will now automatically register
|
|
itself as the `vault` service and perform its own health checks/lifecycle
|
|
status management. This behavior can be adjusted or turned off in Vault's
|
|
configuration; see the
|
|
[documentation](/docs/configuration/index.html#check_timeout)
|
|
for details.
|