5.9.0 (April 22, 2026)
BREAKING CHANGES:
- Renamed all Vault 2.0 pki-external-ca resources from version 5.8.0 to a common prefix of
vault_pki_external_ca_. (#2838)
FEATURES:
- New Resources: Add support for OS Secrets Engine with
vault_os_secret_backend,vault_os_secret_backend_host, andvault_os_secret_backend_accountresources for managing operating system credentials via SSH. Requires Vault 2.0.0+. (#2865) - New Resources:
vault_rotation_policyfor managing rotation policies. Requires Vault 2.0.0+. (#2844) - Add support for
vault_quota_configresource. (#2837) - New Resources: Add support for Vault Key Management secrets engine with resources for managing KMS providers (AWS KMS, Azure Key Vault, GCP Cloud KMS), cryptographic keys, key distribution, replication, and rotation (Vault Enterprise). (#2802)
- New Resources:
vault_alicloud_secret_backend,vault_alicloud_secret_backend_role, and ephemeral resourcevault_alicloud_access_credentialsfor managing AliCloud secrets engine. (#2858, #2874) - New Resource:
vault_plugin_runtimefor managing plugin runtimes in Vault's plugin runtimes catalog. Requires Vault 1.15 or later.(#2835) - Add support for CORS configuration:
vault_sys_config_corsresource and data source for managing and reading Vault's CORS (Cross-Origin Resource Sharing) settings. (#2849) - New Ephemeral Resource: Add vault_generic_endpoint ephemeral resource with response field extraction from data, auth, wrap_info, and lease metadata.(#2830)
IMPROVEMENTS:
vault_cf_auth_backend_config: Addedcf_password_wo_versionto trigger updates when onlycf_password_wochanges.(#2878)vault_pki_secret_backend_config_acme: Added new fields that control the PKI ACME challenge worker IP ranges that they can connect. ([#2839]#2839)- Add support for metadata fields in
azure_access_credentialsandresource_azure_secret_backend_roleresources. (#2734 - Add support for Enterprise Plugins in
vault_pluginresource. (#2707) vault_ldap_secret_backend: Add self-managed support to ldap secrets engine. Requires Vault Enterprise 2.0+. (#2845)azure_static_role: Add support for importing existing credentials via new Vault import endpoint. (#2756)- Updated dependencies:
cloud.google.com/go/authv0.18.2 -> v0.20.0cloud.google.com/go/cloudsqlconnv1.4.3 -> v1.20.2cloud.google.com/go/iamv1.7.0 -> v1.9.0filippo.io/edwards25519v1.1.1 -> v1.2.0github.com/Azure/azure-sdk-for-go/sdk/azcorev1.21.0 -> v1.21.1github.com/Azure/azure-sdk-for-go/sdk/internalv1.11.2 -> v1.12.0github.com/aws/aws-sdk-go-v2v1.41.5 -> v1.41.6github.com/aws/aws-sdk-go-v2/internal/configsourcesv1.4.21 -> v1.4.22github.com/aws/aws-sdk-go-v2/internal/endpoints/v2v2.7.21 -> v2.7.22github.com/aws/aws-sdk-go-v2/service/iamv1.53.7 -> v1.53.8github.com/aws/aws-sdk-go-v2/service/internal/accept-encodingv1.13.7 -> v1.13.8github.com/aws/aws-sdk-go-v2/service/internal/presigned-urlv1.13.21 -> v1.13.22github.com/aws/aws-sdk-go-v2/service/stsv1.41.10 -> v1.42.0github.com/aws/smithy-gov1.24.3 -> v1.25.0github.com/docker/dockerv28.3.3+incompatible -> v28.5.2+incompatiblegithub.com/docker/go-connectionsv0.5.0 -> v0.7.0github.com/fatih/colorv1.18.0 -> v1.19.0github.com/go-jose/go-jose/v3v3.0.4 -> v3.0.5github.com/go-jose/go-jose/v4v4.1.3 -> v4.1.4github.com/googleapis/gax-go/v2v2.20.0 -> v2.21.0github.com/hashicorp/consul/apiv1.33.7 -> v1.34.1github.com/hashicorp/go-secure-stdlib/plugincontainerv0.4.2 -> v0.5.0github.com/hashicorp/terraform-plugin-muxv0.23.0 -> v0.23.1github.com/hashicorp/vault/sdkv0.25.0 -> v0.25.1github.com/jackc/pgtypev1.14.3 -> v1.14.4github.com/oklog/runv1.1.0 -> v1.2.0github.com/opencontainers/image-specv1.1.0 -> v1.1.1go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpcv0.61.0 -> v0.67.0go.opentelemetry.io/contrib/instrumentation/net/http/otelhttpv0.61.0 -> v0.67.0go.opentelemetry.io/otelv1.42.0 -> v1.43.0go.opentelemetry.io/otel/metricv1.42.0 -> v1.43.0go.opentelemetry.io/otel/tracev1.42.0 -> v1.43.0golang.org/x/cryptov0.49.0 -> v0.50.0golang.org/x/modv0.33.0 -> v0.34.0golang.org/x/netv0.52.0 -> v0.53.0golang.org/x/sysv0.42.0 -> v0.43.0golang.org/x/textv0.35.0 -> v0.36.0golang.org/x/toolsv0.42.0 -> v0.43.0google.golang.org/apiv0.273.1 -> v0.276.0google.golang.org/genprotov0.0.0-20260319201613-d00831a3d3e7 -> v0.0.0-20260420184626-e10c466a9529google.golang.org/genproto/googleapis/apiv0.0.0-20260401001100-f93e5f3e9f0f -> v0.0.0-20260414002931-afd174a4e478google.golang.org/genproto/googleapis/rpcv0.0.0-20260319201613-d00831a3d3e7 -> v0.0.0-20260414002931-afd174a4e478google.golang.org/grpcv1.79.3 -> v1.80.0k8s.io/utilsv0.0.0-20260210185600-b8788abfbbc2 -> v0.0.0-20260319190234-28399d86e0b5
BUGS:
vault_consul_secret_backend: Fixed validation logic to allow computed token values by correcting the condition that checks for token presence during plan phase. (#2823)vault_pki_external_ca_secret_backend_acme_account: Provide eab_kid and eab_key values through the ACME account creation request. ([#2851]#2852)provider/auth_login: Fix "Missing Region" error when using genericauth_loginblock for AWS authentication without explicitsts_regionparameter. The provider now properly resolves AWS region from environment variables (AWS_REGION,AWS_DEFAULT_REGION) and EC2 instance metadata service (IMDS), consistent withauth_login_awsbehavior. (#2786)provider/auth_aws: Fixauth_login_awsfor Vault AWS auth backends configured withuse_sts_region_from_client = trueby generating a standard SigV4-signedGetCallerIdentityrequest with anAuthorizationheader, and added support for custom STS endpoints. (#2841)resource_database_secret_backend_connection: Fixes a regression issue forresource_database_secret_backend_connectionfor elasticsearch. Reverted the field name from insecure_tls to insecure.vault_rabbitmq_secret_backend_role: Fixed spurious diff issue forvhostandvhost_topicfields by changing field type from TypeList to TypeSet. (#2872)provider/auth_aws: Fixauth_login_awsto avoid an unintended second STSAssumeRolecall during web identity credential flows, while preserving manual role assumption for explicitly configured or env-derivedaws_role_arnvalues in non-web-identity setups.(#2850)
Release Note:
- Vault Version Support: The Vault provider will be dropping Vault version support for Vault <=
1.18.x. This means that going forward only Vault server version1.19.xand greater will be officially tested against.