Update Terraform vault to v4 - abandoned#473
Open
renovate[bot] wants to merge 11 commits intomainfrom
Open
Conversation
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Contributor
Author
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
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.4.0Release Notes
hashicorp/terraform-provider-vault (vault)
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)github.com/hashicorp/vaultpackage: (#2251)custom_tagsandsecret_name_templatefields tovault_secrets_sync_azure_destinationresource (#2247)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 was generated by Mend Renovate. View the repository job log.