Adding PGX change to release & upgrade notes (#16613)
Also some heading size tidying
This commit is contained in:
parent
67339b71e8
commit
b7365df464
|
@ -100,6 +100,8 @@ Two new enhancements were made to the Transform secrets engine. The first is Con
|
|||
|
||||
Previously, KMIP did not support certain operations such as import, decrypt, encrypt, and query. These operations are now supported. For a complete list of supported KMIP operations, please refer to the [Supported KMIP Operations](/docs/secrets/kmip) documentation.
|
||||
|
||||
@include 'pgx-params.mdx'
|
||||
|
||||
## Known issues
|
||||
|
||||
There are no known issues documented for this release.
|
||||
|
|
|
@ -91,7 +91,7 @@ to understand how the built-in resources are used in the system.
|
|||
|
||||
@include 'raft-panic-old-tls-key.mdx'
|
||||
|
||||
## Errors returned by perf standbys lagging behind active node with Consul storage
|
||||
### Errors returned by perf standbys lagging behind active node with Consul storage
|
||||
|
||||
The introduction of [Server Side Consistent Tokens](/docs/faq/ssct) means that
|
||||
when issuing a request to a perf standby right after having obtained a token (e.g.
|
||||
|
|
|
@ -19,6 +19,10 @@ an Elasticsearch version prior to 6, they will need to switch back to the old
|
|||
API path by setting the [bool config option](/api-docs/secret/databases/elasticdb#use_old_xpack)
|
||||
`use_old_xpack=true`.
|
||||
|
||||
## Changes
|
||||
|
||||
@include 'pgx-params.mdx'
|
||||
|
||||
## Known Issues
|
||||
|
||||
@include 'raft-retry-join-failure.mdx'
|
||||
|
|
|
@ -40,13 +40,10 @@ Notes](https://golang.org/doc/go1.16) for full details. Of particular note:
|
|||
|
||||
@include 'alpine-314.mdx'
|
||||
|
||||
|
||||
@include 'entity-alias-mapping.mdx'
|
||||
|
||||
@include 'pki-forwarding-bug.mdx'
|
||||
|
||||
@include 'raft-panic-old-tls-key.mdx'
|
||||
|
||||
## Known Issues
|
||||
|
||||
@include 'raft-panic-old-tls-key.mdx'
|
||||
|
|
|
@ -0,0 +1,5 @@
|
|||
### Postgres Library Change
|
||||
|
||||
Vault 1.11+ uses pgx instead of lib/pq for Postgres connections. If you are
|
||||
using parameters like `fallback_application_name` that pgx does not support, you
|
||||
may need to update your `connection_url` before upgrading to Vault 1.11+.
|
|
@ -1,4 +1,4 @@
|
|||
## Integrated Storage panic related to old TLS key
|
||||
### Integrated Storage panic related to old TLS key
|
||||
|
||||
Raft in Vault uses its own set of TLS certificates, independent of those that the user
|
||||
controls to protect the API port and those used for replication and clustering. These
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
## Cluster initialization hangs with `retry_join`
|
||||
### Cluster initialization hangs with `retry_join`
|
||||
|
||||
The
|
||||
[`retry_join`](/docs/concepts/integrated-storage/index#retry_join-configuration)
|
||||
|
@ -13,7 +13,7 @@ The bug was introduced by commit
|
|||
https://github.com/hashicorp/vault/commit/cc6409222ce246ed72d067debe6ffeb8f62f9dad
|
||||
and first reported in https://github.com/hashicorp/vault/issues/16486.
|
||||
|
||||
### Impacted Versions
|
||||
#### Impacted Versions
|
||||
|
||||
Affects versions 1.11.1 and 1.10.5. Versions prior to these are unaffected.
|
||||
|
||||
|
|
Loading…
Reference in New Issue