mirror of
https://github.com/optim-enterprises-bv/vault.git
synced 2025-10-29 09:42:25 +00:00
64b50ad7a1
* When support for service tags was added, the only way we had to parse and dedup a list of strings also forced them to be lowercase. Now there's another helper func that doesn't smash the case so use that instead. * update Consul 'service_tag' documentation to include case sensitivity * added upgrade guide for 1.15 * test for service tags Co-authored-by: Nick Cabatoff <ncabatoff@hashicorp.com> Co-authored-by: Peter Wilson <peter.wilson@hashicorp.com>
35 lines
1.2 KiB
Plaintext
35 lines
1.2 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Upgrade to Vault 1.15.x - Guides
|
|
description: |-
|
|
Deprecations, important or breaking changes, and remediation recommendations
|
|
for anyone upgrading to 1.15.x from Vault 1.14.x.
|
|
---
|
|
|
|
# Overview
|
|
|
|
The Vault 1.15.x upgrade guide contains information on deprecations, important
|
|
or breaking changes, and remediation recommendations for anyone upgrading from
|
|
Vault 1.14. **Please read carefully**.
|
|
|
|
## Consul service registration
|
|
|
|
As of version 1.15, `service_tags` supplied to Vault for the purpose of [Consul
|
|
service registration](/vault/docs/configuration/service-registration/consul#service_tags)
|
|
will be **case-sensitive**.
|
|
|
|
In previous versions of Vault tags were converted to lowercase which led to issues,
|
|
for example when tags contained Traefik rules which use case-sensitive method names
|
|
such as `Host()`.
|
|
|
|
If you previously used Consul service registration tags ignoring case, or relied
|
|
on the lowercase tags created by Vault, then this change may cause unexpected behavior.
|
|
|
|
Please audit your Consul storage stanza to ensure that you either:
|
|
|
|
* Manually convert your `service_tags` to lowercase if required
|
|
* Ensure that any system that relies on the tags is aware of the new case-preserving behavior
|
|
|
|
|
|
|