Releases: hashicorp/terraform-provider-vault
Releases · hashicorp/terraform-provider-vault
v3.13.0
FEATURES:
- Add new resource for AWS Auth Backend config identity: (#1724)
- Support
default_user_template
field onvault_ssh_secret_backend_role
: (#1725)
IMPROVEMENTS:
- Secrets from the AD, AWS, Azure & Nomad Secrets Engines are sensitive: (#1726)
- Add enterprise check for new Raft Autopilot parameter: (#1721)
BUGS:
v3.12.0
IMPROVEMENTS:
- Add support for importing the PKI CRL config: (#1710)
- Ensure duplicate alias names are handled properly in LookupEntityAlias: (#1708)
- Add support for a Raft Autopilot State datasource: (#1705)
- Add support for adding metadata to a KV V2 Secret: (#1687)
- Set AWS credentials sensitive: (#1678)
- Set ForceNew on the path field of namespaces: (#1713)
BUGS:
v3.11.0
v3.10.0
v3.9.1
v3.9.0
IMPROVEMENTS:
- Add first-class Azure login support: (#1617)
- Add first-class OIDC andJWT login support: (#1615)
- Add first-class OCI login support: (#1614)
- Add first-class Radius login support: (#1609)
- Add first-class Kerberos login support: (#1608)
- Add first-class GCP login support: (#1607)
- Add first-class TLS certificates login support: (#1605)
- Add first-class auth login config support for AWS: (#1599) (#1618)
- Add support for login MFA resources: (#1620)
- Add Managed Keys support: (#1508)
- Add support to perform semantic version comparisons against Vault's server version: (#1426)
- Add Mount Migration support to all secrets/auth backends: (#1594)
- Use new semantic version checking for Consul secrets backend logic: (#1593)
- Docs: Fix vault_kv_secret_backend_v2 delete_version_after example: (#1602)
- Support creating Azure secret backend role by specifying the role_id: (#1573)
- Add Redis ElastiCache database secrets engine support: (#1596)
- vault_pki_secret_backend_cert: Report when renewal is pending: (#1597)
- Accept data source values in the token field for Consul secrets backend: (#1600)
BUGS:
v3.8.2
IMPROVEMENTS:
BUGS:
- fix: remove unnecessary nesting of secret data for KV-V1 secrets: (#1570)
NOTES:
vault_kv_secret
no longer stores secrets in Vault under a nesteddata
object.
In versions 3.8.1 and below, the kv resource inadvertently nested thevalue
underdata
.
To remedy this please update any consumers of this KV and run aterraform apply
to properly set the value.
v3.8.1
v3.8.0
FEATURES:
- Adds support for Kubernetes secrets engine:
(#1515) - PKI: Add support for CPS URL in custom policy identifiers:
(#1495)
IMPROVEMENTS:
- Fix Import for OIDC Scope resource:
(#1548) - Update entity alias creation to use entity lookup api:
(#1517)
(#1552) - Add support for Consul secrets engine enhancements:
(#1518) - auth/gcp: adds
custom_endpoint
parameter to backend config:
(#1482) - auth/jwt: adds
user_claim_json_pointer
andmax_age
to roles:
(#1478)
BUGS:
- Support updating backend descriptions:
(#1550)
(#1543) - Properly set the
base64_pem
in Vault for Couchbase:
(#1545) - Fix bug where some rabbitmq config changes trigger erroneous mount recreation:
(#1542) - Update
*kv_secrets*
resources to support namespaces:
(#1529) - Do not validate JSON on OIDC scope template:
(#1547)
v3.7.0
FEATURES:
- Support setting
namespace
by resource
(#1305)
(#1479) - Add dedicated KV (v1/v2) secret engine resources, and data sources, supersedes
vault_generic_secret
(#1457)
IMPROVEMENTS:
- Update vault libs to v1.10.3
(#1483) - Drop debug log calls containing the full vault response
(#1477) resource/token
: Addmetadata
support
(#1470)resource/vault_ldap_auth_backend
: support LDAPusername_as_alias
attribute:
(#1460)resource/vault_quota_rate_limit
: Add support forinterval
andblock_interval
:
(#1084)- ci: Test against vault-enterprise 1.10.3-ent:
(#1461)
BUGS: