breaking: the dependency vault has been updated to a new major version (4.8.0), which may include breaking changes. #major#459
Open
public-glueops-renovatebot[bot] wants to merge 1 commit intomainfrom
Conversation
vault has been updated to a new major version (v4.8.0), which may include breaking changes. #majorvault has been updated to a new major version (4.8.0), which may include breaking changes. #major
d0c058f to
650550c
Compare
52833c3 to
55f00ad
Compare
a1fb16d to
33fada5
Compare
02b7788 to
a6f8a88
Compare
28788a6 to
38189fc
Compare
38189fc to
e2333d5
Compare
e2333d5 to
a7faa71
Compare
f7f8ce2 to
090b3b3
Compare
c1d39ce to
5901c0e
Compare
e7a3a94 to
226e9a2
Compare
226e9a2 to
0798407
Compare
…ion (4.8.0), which may include breaking changes. #major
0798407 to
a00f1e8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.25.0→4.8.0Release Notes
hashicorp/terraform-provider-vault (vault)
v4.8.0Compare Source
FEATURES:
recursivesearch indata_vault_namespaces#2408subscribe_event_typesindata_source_policy_document#2445explicit_max_ttlinvault_azure_secret_backend_roleresources. Requires Vault 1.18+ (#2438).BUGS:
vault_azure_access_credentialsdata source caused by Azure RBAC propagation delays usingazure_groups#2437v4.7.0Compare Source
FEATURES:
vault_pki_secret_backend_root_certandvault_pki_secret_backend_root_sign_intermediateto support the new fields for the name constraints extension. Requires Vault 1.19+ (#2396).vault_pki_secret_backend_issuerresource with the new issuer configuration fields to control certificate verification. Requires Vault Enterprise 1.19+ (#2400).revoke_with_keyinvault_pki_secret_backend_cert(#2242)vault_pki_secret_backend_role,vault_pki_secret_backend_root_cert,vault_pki_secret_backend_root_sign_intermediateandvault_pki_secret_backend_intermediate_cert_request([#2401])(#2401)vault_pki_secret_backend_intermediate_cert_request([#2404])(#2404)skip_import_rotationinvault_database_secret_backend_static_role. Requires Vault Enterprise 1.18.5+ (#2386).not_afterinvault_pki_secret_backend_cert,vault_pki_secret_backend_role,vault_pki_secret_backend_root_cert,vault_pki_secret_backend_root_sign_intermediate, andvault_pki_secret_backend_sign(#2385).vault_pki_secret_backend_config_acmeto support themax_ttlfield. #2411vault_ssh_secret_backend_sign. (#2409)disabled_validationsinvault_pki_secret_backend_config_cmpv2#2412credential_typeandcredential_configtodatabase_secret_backend_static_roleto support features like rsa keys for Snowflake DB engines with static roles #2384vault_pki_secret_backend_root_sign_intermediate:not_before_duration,skidanduse_pss#2417use_pss,no_store_metadata, andserial_number_sourcetovault_pki_secret_backend_role#2420signandverifyendpoints (#2418)vault_pki_secret_backend_cert_metadataand support forcert_metadatainvault_pki_secret_backend_certandvault_pki_secret_backend_sign#2422max_crl_entriesinvault_pki_secret_backend_crl_config#2423vault_pki_secret_backend_config_auto_tidyto set PKI automatic tidy configuration #1934BUGS:
IMPROVEMENTS:
v4.6.0Compare Source
FEATURES:
vault_kubernetes_auth_backend_roleto supportbound_service_account_namespace_selector, enabling the use of namespace selectors for allowing Kubernetes namespaces to access roles. (#2379)vault_database_secret_backend_connectionto supportpassword_authenticationfor PostgreSQL, allowing to encrypt password before being passed to PostgreSQL (#2371)external_idfield for thevault_aws_auth_backend_sts_roleresource (#2370)vault_pki_secret_backend_config_acmeresource. Requires Vault 1.14+ (#2157).vault_pki_secret_backend_roleto support thecn_validationsrole field (#1820).vault_pki_secret_backend_acme_eabto manage PKI ACME external account binding tokens. Requires Vault 1.14+. (#2367)vault_pki_secret_backend_config_cmpv2. Requires Vault 1.18+. Available only for Vault Enterprise (#2330)IMPROVEMENTS:
subscribepolicy capability forvault_policy_documentdata source (#2293)v4.5.0Compare Source
FEATURES:
vault_database_secret_backend_connectionto support inline TLS config for PostgreSQL (#2339)vault_database_secret_backend_connectionto support skip_verification config for Cassandra (#2346)vault_approle_auth_backend_role_secret_idto supportnum_usesandttlfields (#2345)allow_empty_principalsfield for thevault_ssh_secret_backend_roleresource (#2354)vault_gcp_secret_impersonated_accountto support settingttl(#2318)connection_timeoutfield for thevault_ldap_auth_backendresource (#2358)use_annotations_as_alias_metadatafield for thevault_kubernetes_auth_backend_configresource (#2226)BUGS:
v4.4.0Compare Source
FEATURES:
vault_aws_secret_backend_roleto support settingsession_tagsandexternal_id(#2290)BUGS:
vault_ssh_secret_backend_cawhere a schema change forced the resource to be replaced (#2308)v4.3.0Compare Source
FEATURES:
iam_tagsinvault_aws_secret_backend_role(#2231).inheritableonvault_quota_rate_limitandvault_quota_lease_count. Requires Vault 1.15+.: (#2133).vault_gcp_secret_backend. Requires Vault 1.17+. Available only for Vault Enterprise (#2249).vault_azure_secret_backend. Requires Vault 1.17+. Available only for Vault Enterprise (#2250)vault_aws_auth_backend_client. Requires Vault 1.17+. Available only for Vault Enterprise (#2243).vault_gcp_auth_backend(#2256)vault_azure_auth_backend_config. Requires Vault 1.17+. Available only for Vault Enterprise (#2254).vault_pki_secret_backend_config_est. Requires Vault 1.16+. Available only for Vault Enterprise (#2246)vault_okta_auth_backendresource: (#2210)max_retriesinvault_aws_auth_backend_client: (#2270)vault_pluginandvault_plugin_pinned_version: (#2159)key_typeandkey_bitstovault_ssh_secret_backend_ca: (#1454)IMPROVEMENTS:
vault_jwt_auth_backend_roleresource: (#2232)BUGS:
github.com/hashicorp/vaultpackage: (#2251)custom_tagsandsecret_name_templatefields tovault_secrets_sync_azure_destinationresource (#2247)max_path_lengthinvault_pki_secret_backend_root_certandvault_pki_secret_backend_root_sign_intermediateresources (#2253)v4.2.0Compare Source
FEATURES:
granularityto Secrets Sync destination resources. Requires Vault 1.16+ Enterprise. (#2202)allowed_kubernetes_namespace_selectorinvault_kubernetes_secret_backend_role(#2180).vault_namespace. Requires Vault Enterprise: (#2208).vault_namespaces. Requires Vault Enterprise: (#2212).IMPROVEMENTS:
BUGS:
vault_approle_auth_backend_role_secret_idregression to handle 404 errors (#2204)vault_kv_secretandvault_kv_secret_v2failure to update secret data modified outside terraform (#2207)vault_kv_secret_v2failing on imported resource when data_json should be ignored (#2207)v4.1.0Compare Source
CHANGES TO VAULT POLICY REQUIREMENTS:
The v4.0.0 release required read permissions at
sys/auth/:pathwhich was asudo endpoint. The v4.1.0 release changed that to instead require permissions
at the
sys/mounts/auth/:pathlevel and sudo is no longer required. Pleaserefer to the details in the Terraform Vault Provider 4.0.0 Upgrade Guide.
FEATURES:
vault_config_ui_custom_message. Requires Vault 1.16+ Enterprise: (#2154).IMPROVEMENTS:
BUGS:
vault_azure_access_credentialsto default to Azure Public Cloud (#2190)v4.0.0Compare Source
Important: This release requires read policies to be set at the path level for mount metadata.
For example, instead of permissions at
sys/authyou must set permissions atthe
sys/auth/:pathlevel. Please refer to the details in theTerraform Vault Provider 4.0.0 Upgrade Guide.
FEATURES:
vault_pki_secret_backend_config_clusterresource. Requires Vault 1.13+ (#1949).enable_templatinginvault_pki_secret_backend_config_urls(#2147).skip_import_rotationandskip_static_role_import_rotationinldap_secret_backend_static_roleandldap_secret_backendrespectively. Requires Vault 1.16+ (#2128).vault_pluginandvault_plugin_pinned_versionresources for managing external plugins (#2159)IMPROVEMENTS:
versionin returned values forvault_kv_secret_v2data source: (#2095)BUGS:
vault_ldap_secret_backend_static_role,vault_ldap_secret_backend_library_set, andvault_ldap_secret_backend_static_role(#2156).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.