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
41 lines
2 KiB
Markdown
41 lines
2 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Upgrading to Vault 0.7.0 - Guides"
|
|
sidebar_title: "Upgrade to 0.7.0"
|
|
sidebar_current: "docs-upgrading-to-0.7.0"
|
|
description: |-
|
|
This page contains the list of deprecations and important or breaking changes
|
|
for Vault 0.7.0. Please read it carefully.
|
|
---
|
|
|
|
# Overview
|
|
|
|
This page contains the list of deprecations and important or breaking changes
|
|
for Vault 0.7.0 compared to the most recent release. Please read it carefully.
|
|
|
|
## List Operations Always Use Trailing Slash
|
|
|
|
Any list operation, whether via the `GET` or `LIST` HTTP verb, will now
|
|
internally canonicalize the path to have a trailing slash. This makes policy
|
|
writing more predictable, as it means clients will no longer work or fail
|
|
based on which client they're using or which HTTP verb they're using. However,
|
|
it also means that policies allowing `list` capability must be carefully
|
|
checked to ensure that they contain a trailing slash; some policies may need
|
|
to be split into multiple stanzas to accommodate.
|
|
|
|
## PKI Defaults to Unleased Certificates
|
|
|
|
When issuing certificates from the PKI backend, by default, no leases will be
|
|
issued. If you want to manually revoke a certificate, its serial number can be
|
|
used with the `pki/revoke` endpoint. Issuing leases is still possible by
|
|
enabling the `generate_lease` toggle in PKI role entries (this will default to
|
|
`true` for upgrades, to keep existing behavior), which will allow using lease
|
|
IDs to revoke certificates. For installations issuing large numbers of
|
|
certificates (tens to hundreds of thousands, or millions), this will
|
|
significantly improve Vault startup time since leases associated with these
|
|
certificates will not have to be loaded; however note that it also means that
|
|
revocation of a token used to issue certificates will no longer add these
|
|
certificates to a CRL. If this behavior is desired or needed, consider keeping
|
|
leases enabled and ensuring lifetimes are reasonable, and issue long-lived
|
|
certificates via a different role with leases disabled.
|