The words "can be" were missing

* fixed broken links

* Update ha.mdx

removed extra slash

* auth/cert: Add certificate extensions as metadata
Signed-off-by: Peter Verraedt <peter.verraedt@kuleuven.be>

* Add changelog for #13348
Signed-off-by: Peter Verraedt <peter.verraedt@kuleuven.be>

* Update docs to reflect that TLS connection state is now available to plugins

* Fix typo (D'oh!)

fix(docs-k8s-helm): changed server's podAntiAffinity labelSelector example to match helm default values (#13140)

* Update algolia-index.yml

* Generate the file

* Update <Subnav />

* Upgrade to latest/upgrade product downloads

* docs: add a note regarding the backend => storage config key aliasing

This was missing from upgrade docs and implemented in #2456.

* Update website/content/docs/upgrading/upgrade-to-0.7.0.mdx
Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com>
Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com>

* Attempt to address a data race issue within identity store
* Testcase TestIdentityStore_LocalAliasInvalidations identified a data race issue.
* This reverts the previous attempt to address the issue from #13093

* Adding upgrade note about 1.7.8 go version

* Adding version bump while I'm at it

Fixes an issue where the `replicateStateStore` was being set to `nil`
upon consecutive calls to `client.SetReadYourWrites(true)`.

* Fixed null token panic from 'v1/auth/token/' endpoints and returned proper error response

* added changelog entry for PR #13233

* changed error message from 'bad token' to 'null token'

* rebased off of main

* Revert "changed error message from 'bad token' to 'null token'"

This reverts commit 381ed9b32c5ddd5e47adb1643ef7e46fb768bc76.

* changed 'bad token' error message to 'invalid token' after revert

* remove unnecessary vault-data folder

We don't check for errors in the consul storage TLS setup. We might fail here
because of a missing certificate, bad permissions, etc. If anything is wrong,
vault just ignores the issues and continues, resulting in a lot of confusion.

Instead, lets return an error to the caller if this fails.

* add tencentCloud plugin

* add tencentCloud plugin

* add tencentCloud plugin

* fixes some flaky enterprise tests

* more test fixes

* Changes to bring ENT in line with OSS for managed key changes

* Revert this

* Improve databases documentation

Fixed a bunch of formatting issues and broken JSON outputs.

* Remove changelog entry

* Apply suggestions from code review

* Update entity-alias.mdx

it was not clear for approle what the name should be the approle name or the role_id.

* Update website/content/api-docs/secret/identity/entity-alias.mdx
Co-authored-by: Yoko Hyakuna <yoko@hashicorp.com>
Co-authored-by: Yoko Hyakuna <yoko@hashicorp.com>

Fix typo in Kubernetes policy example which prevents example from working.

* Upgrade guidance updates from VLT-172

Trying to clarify some upgrade questions. Learn update to follow in
separate PR.

* Apply suggestions from code review
Co-authored-by: Nick Cabatoff <ncabatoff@hashicorp.com>
Co-authored-by: Nick Cabatoff <ncabatoff@hashicorp.com>

Previously the `contained_db` parameter would only accept a string value
despite the fact that field type is documented as a boolean.

Co-authored-by: tograla <tograla@gmail.com>

* Update index.mdx

Fixed typo in Setup section of the Secrets Engine documentation.

* Update index.mdx

Remove line 112.