From b3f5b5948fe3b9d6b681d7a2a6010842e7878c6f Mon Sep 17 00:00:00 2001 From: Brian Kassouf Date: Tue, 2 Oct 2018 15:15:46 -0700 Subject: [PATCH 01/24] changelog++ --- CHANGELOG.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index ea3ff3cc6..ac9426b54 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -50,6 +50,7 @@ IMPROVEMENTS: * storage/zookeeper: Enable TLS based communication with Zookeeper [GH-4856] * ui: you can now init a cluster with a seal config [GH-5428] * ui: added the option to force promote replication clusters [GH-5438] + * replication: Allow promotion of a secondary when data is syncing with a "force" flag ## 0.11.1.1 (September 17th, 2018) (Enterprise Only) From 0cd93c48c0b8a42b13e5ea462204dbe34ed02500 Mon Sep 17 00:00:00 2001 From: Chris Hoffman Date: Tue, 2 Oct 2018 20:18:59 -0400 Subject: [PATCH 02/24] adding upgrade guide (#5447) --- .../upgrading/upgrade-to-0.11.2.html.md | 24 +++++++++++++++++++ website/source/layouts/guides.erb | 3 +++ 2 files changed, 27 insertions(+) create mode 100644 website/source/guides/upgrading/upgrade-to-0.11.2.html.md diff --git a/website/source/guides/upgrading/upgrade-to-0.11.2.html.md b/website/source/guides/upgrading/upgrade-to-0.11.2.html.md new file mode 100644 index 000000000..cbcb05b39 --- /dev/null +++ b/website/source/guides/upgrading/upgrade-to-0.11.2.html.md @@ -0,0 +1,24 @@ +--- +layout: "guides" +page_title: "Upgrading to Vault 0.11.2 - Guides" +sidebar_current: "guides-upgrading-to-0.11.2" +description: |- + This page contains the list of deprecations and important or breaking changes + for Vault 0.11.2. Please read it carefully. +--- + +# Overview + +This page contains the list of deprecations and important or breaking changes +for Vault 0.11.2 compared to 0.11.1. Please read it carefully. + +### `sys/seal-status` Behavior Change + +The `sys/seal-status` endpoint now includes an initialized boolean in the +output. If Vault is not initialized, it will return a 200 with this value +set false instead of a 400 + +### Mount Config Passthrough Headers + +The mount config option for `passthrough_request_headers` will now deny +certain headers from being provided to backends based on a global denylist. diff --git a/website/source/layouts/guides.erb b/website/source/layouts/guides.erb index 9261a37c3..99ebb937f 100644 --- a/website/source/layouts/guides.erb +++ b/website/source/layouts/guides.erb @@ -197,6 +197,9 @@ > Upgrade to 0.11.0 + > + Upgrade to 0.11.2 + From 7409777888adca8ba3a6ca1d212013864cd1b320 Mon Sep 17 00:00:00 2001 From: Becca Petrin Date: Tue, 2 Oct 2018 17:21:26 -0700 Subject: [PATCH 03/24] alicloud auto-unseal docs (#5446) --- .../configuration/seal/alicloudkms.html.md | 90 +++++++++++++++++++ website/source/layouts/docs.erb | 3 + 2 files changed, 93 insertions(+) create mode 100644 website/source/docs/configuration/seal/alicloudkms.html.md diff --git a/website/source/docs/configuration/seal/alicloudkms.html.md b/website/source/docs/configuration/seal/alicloudkms.html.md new file mode 100644 index 000000000..47f40643c --- /dev/null +++ b/website/source/docs/configuration/seal/alicloudkms.html.md @@ -0,0 +1,90 @@ +--- +layout: "docs" +page_title: "AliCloud KMS - Seals - Configuration" +sidebar_current: "docs-configuration-seal-alicloudkms" +description: |- + The AliCloud KMS seal configures Vault to use AliCloud KMS as the seal wrapping + mechanism. +--- + +# `alicloudkms` Seal + +The AliCloud KMS seal configures Vault to use AliCloud KMS as the seal wrapping mechanism. +Vault Enterprise's AliCloud KMS seal is activated by one of the following: + +* The presence of a `seal "alicloudkms"` block in Vault's configuration file. +* The presence of the environment variable `VAULT_SEAL_TYPE` set to `alicloudkms`. If + enabling via environment variable, all other required values specific to AliCloud + KMS (i.e. `VAULT_ALICLOUDKMS_SEAL_KEY_ID`) must be also supplied, as well as all + other AliCloud-related environment variables that lends to successful + authentication. + +## `alicloudkms` Example + +This example shows configuring AliCloud KMS seal through the Vault configuration file +by providing all the required values: + +```hcl +seal "alicloudkms" { + region = "us-east-1" + access_key = "0wNEpMMlzy7szvai" + secret_key = "PupkTg8jdmau1cXxYacgE736PJj4cA" + kms_key_id = "08c33a6f-4e0a-4a1b-a3fa-7ddfa1d4fb73" +} +``` + +## `alicloudkms` Parameters + +These parameters apply to the `seal` stanza in the Vault configuration file: + +- `region` `(string: "us-east-1")`: The AliCloud region where the encryption key + lives. May also be specified by the `ALICLOUD_REGION` + environment variable. + +- `domain` `(string: "kms.us-east-1.aliyuncs.com")`: If set, overrides the endpoint + AliCloud would normally use for KMS for a particular region. May also be specified + by the `ALICLOUD_DOMAIN` environment variable. + +- `access_key` `(string: )`: The AliCloud access key ID to use. May also be + specified by the `ALICLOUD_ACCESS_KEY` environment variable or as part of the + AliCloud profile from the AliCloud CLI or instance profile. + +- `secret_key` `(string: )`: The AliCloud secret access key to use. May + also be specified by the `ALICLOUD_SECRET_KEY` environment variable or as + part of the AliCloud profile from the AliCloud CLI or instance profile. + +- `kms_key_id` `(string: )`: The AliCloud KMS key ID to use for encryption + and decryption. May also be specified by the `VAULT_ALICLOUDKMS_SEAL_KEY_ID` + environment variable. + +## Authentication + +Authentication-related values must be provided, either as environment +variables or as configuration parameters. + +~> **Note:** Although the configuration file allows you to pass in +`ALICLOUD_ACCESS_KEY` and `ALICLOUD_SECRET_KEY` as part of the seal's parameters, it +is *strongly* recommended to set these values via environment variables. + +```text +AliCloud authentication values: + +* `ALICLOUD_REGION` +* `ALICLOUD_ACCESS_KEY` +* `ALICLOUD_SECRET_KEY` +``` + +Note: The client uses the official AliCloud SDK and will use environment credentials, +the specified credentials, or RAM role credentials in that order. + +## `alicloudkms` Environment Variables + +Alternatively, the AliCloud KMS seal can be activated by providing the following +environment variables: + +```text +Vault Seal specific values: + +* `VAULT_SEAL_TYPE` +* `VAULT_ALICLOUDKMS_SEAL_KEY_ID` +``` diff --git a/website/source/layouts/docs.erb b/website/source/layouts/docs.erb index 407527f6e..08d1afeaf 100644 --- a/website/source/layouts/docs.erb +++ b/website/source/layouts/docs.erb @@ -97,6 +97,9 @@ > seal