Bump vars for 0.9.1
This commit is contained in:
parent
a14ed7f48d
commit
121d5bfeaa
|
@ -1,4 +1,4 @@
|
|||
## 0.9.1 (Unreleased)
|
||||
## 0.9.1 (December 21st, 2017)
|
||||
|
||||
DEPRECATIONS/CHANGES:
|
||||
|
||||
|
@ -26,7 +26,7 @@ DEPRECATIONS/CHANGES:
|
|||
accept both strings and integer numbers of seconds for its lease value. The
|
||||
value returned on a role read will be an integer number of seconds instead
|
||||
of a human-friendly string.
|
||||
* Unprintable characters not allowed in API names: Unprintable characters are
|
||||
* Unprintable characters not allowed in API paths: Unprintable characters are
|
||||
no longer allowed in names in the API (paths and path parameters), with an
|
||||
extra restriction on whitespace characters. Allowed characters are those
|
||||
that are considered printable by Unicode plus spaces.
|
||||
|
|
|
@ -3,7 +3,7 @@
|
|||
//-------------------------------------------------------------------
|
||||
|
||||
variable "download-url" {
|
||||
default = "https://releases.hashicorp.com/vault/0.9.0/vault_0.9.0_linux_amd64.zip"
|
||||
default = "https://releases.hashicorp.com/vault/0.9.1/vault_0.9.1_linux_amd64.zip"
|
||||
description = "URL to download Vault"
|
||||
}
|
||||
|
||||
|
|
|
@ -2,7 +2,7 @@ package version
|
|||
|
||||
func init() {
|
||||
// The main version number that is being run at the moment.
|
||||
Version = "0.9.0"
|
||||
Version = "0.9.1"
|
||||
|
||||
// A pre-release marker for the version. If this is "" (empty string)
|
||||
// then it means that it is a final release. Otherwise, this is a pre-release
|
||||
|
|
|
@ -2,7 +2,7 @@ set :base_url, "https://www.vaultproject.io/"
|
|||
|
||||
activate :hashicorp do |h|
|
||||
h.name = "vault"
|
||||
h.version = "0.9.0"
|
||||
h.version = "0.9.1"
|
||||
h.github_slug = "hashicorp/vault"
|
||||
h.website_root = "website"
|
||||
end
|
||||
|
|
|
@ -0,0 +1,56 @@
|
|||
---
|
||||
layout: "guides"
|
||||
page_title: "Upgrading to Vault 0.9.1 - Guides"
|
||||
sidebar_current: "guides-upgrading-to-0.9.1"
|
||||
description: |-
|
||||
This page contains the list of deprecations and important or breaking changes
|
||||
for Vault 0.9.1. Please read it carefully.
|
||||
---
|
||||
|
||||
# Overview
|
||||
|
||||
This page contains the list of deprecations and important or breaking changes
|
||||
for Vault 0.9.1 compared to the 0.9.0. Please read it carefully.
|
||||
|
||||
### AppRole Case Sensitivity
|
||||
|
||||
In prior versions of Vault, `list` operations against AppRole roles would
|
||||
require preserving case in the role name, even though most other operations
|
||||
within AppRole are case-insensitive with respect to the role name. This has
|
||||
been fixed; existing roles will behave as they have in the past, but new roles
|
||||
will act case-insensitively in these cases.
|
||||
|
||||
### Token Auth Backend Roles Parameter Types
|
||||
|
||||
For `allowed_policies` and `disallowed_policies` in role definitions in the
|
||||
token auth backend, input can now be a comma-separated string or an array of
|
||||
strings. Reading a role will now return arrays for these parameters.
|
||||
|
||||
### Transit Key Exporting
|
||||
|
||||
You can now mark a key in the `transit` backend as `exportable` at any time,
|
||||
rather than just at creation time; however, once this value is set, it still
|
||||
cannot be unset.
|
||||
|
||||
### PKI Secret Backend Roles Parameter Types
|
||||
|
||||
For `allowed_domains` and `key_usage` 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.
|
||||
|
||||
### SSH Dynamic Keys Method Defaults to 2048-bit Keys
|
||||
|
||||
When using the dynamic key method in the SSH backend, the default is now to use
|
||||
2048-bit keys if no specific key bit size is specified.
|
||||
|
||||
### Consul Secret Backend Lease Handling
|
||||
|
||||
The `consul` secret backend can now accept both strings and integer numbers of
|
||||
seconds for its lease value. The value returned on a role read will be an
|
||||
integer number of seconds instead of a human-friendly string.
|
||||
|
||||
### Unprintable Characters Not Allowed in API Paths
|
||||
|
||||
Unprintable characters are no longer allowed in names in the API (paths and
|
||||
path parameters), with an extra restriction on whitespace characters. Allowed
|
||||
characters are those that are considered printable by Unicode plus spaces.
|
|
@ -56,7 +56,9 @@
|
|||
<li<%= sidebar_current("guides-upgrading-to-0.9.0") %>>
|
||||
<a href="/guides/upgrading/upgrade-to-0.9.0.html">Upgrade to 0.9.0</a>
|
||||
</li>
|
||||
|
||||
<li<%= sidebar_current("guides-upgrading-to-0.9.1") %>>
|
||||
<a href="/guides/upgrading/upgrade-to-0.9.1.html">Upgrade to 0.9.1</a>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
|
Loading…
Reference in New Issue