terraform-provider-vault icon indicating copy to clipboard operation
terraform-provider-vault copied to clipboard

Terraform Vault provider

Results 388 terraform-provider-vault issues
Sort by recently updated
recently updated
newest added

### Terraform Version ``` Terraform v1.0.11 on darwin_amd64 + provider registry.terraform.io/hashicorp/google v3.90.1 + provider registry.terraform.io/hashicorp/random v3.1.0 + provider registry.terraform.io/hashicorp/vault v3.0.1 + provider registry.terraform.io/mongodb/mongodbatlas v1.1.1 ``` ### Affected Resource(s) - vault_database_secret_backend_connection...

feature-parity

This change adds `username_template` field to mongodbatlas block in `vault_database_secret_backend_connection` resource. ### Community Note * Please vote on this pull request by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original pull...

documentation
size/XS

### Terraform Core Version 1.6.4 ### Terraform Vault Provider Version 3.23.0 ### Vault Server Version 1.15.1+ent ### Affected Resource(s) Similar to #1964, the new `vault_saml_auth_backend` doesn't seem to have an...

bug

The [aws_secret_backend](https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/aws_secret_backend) resource includes [default_lease_ttl_seconds](https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/aws_secret_backend#default_lease_ttl_seconds) and [max_lease_ttl_seconds](https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/aws_secret_backend#max_lease_ttl_seconds). These seem to relate to generic [Mount tuning](https://www.vaultproject.io/api-docs/system/mounts#tune-mount-configuration) instead of the AWS-specific [lease configuration](https://www.vaultproject.io/api-docs/secret/aws#configure-lease). This is fine, but a little misleading. IMHO there...

Hi there, Vault supports the `iam_tags` option when creating dynamic AWS roles (see https://www.vaultproject.io/api/secret/aws#iam_tags). Unfortunately, the Terraform Vault provider doesn't support this (see https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/aws_secret_backend_role), similar to the `permissions_boundary_arn` referenced in...

### Terraform Core Version 1.6.3 ### Terraform Vault Provider Version 3.21.0 ### Vault Server Version 1.15.0 ### Affected Resource(s) * vault_azure_access_credentials ### Expected Behavior The credentials returned by `vault_azure_access_credentials` should...

bug

### Terraform Core Version 0.13.2 ### Terraform Vault Provider Version 3.21.0 ### Vault Server Version 1.14.4 ### Affected Resource(s) * `vault_database_secret_backend_connection` ### Expected Behavior Read should happen ### Actual Behavior...

bug

### Documentation Link https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/namespace#namespace ### Description the second `namespace` hyperlink (in "relative to the provider's configured namespace") which refers to https://registry.terraform.io/docs/providers/vault#namespace , returns a 404. ### References https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/namespace Section in...

documentation

### Terraform Core Version 1.6.3 ### Terraform Vault Provider Version 3.22.0 ### Vault Server Version 1.11.4 ### Affected Resource(s) * database_secret_backend_connection ### Expected Behavior If the `connection_url` is changed outside...

bug

I've got these environment variables defined: - AWS_SECRET_ACCESS_KEY - AWS_ACCESS_KEY_ID - AWS_SESSION_TOKEN ### Terraform Version v1.3.7 ### Affected Resource(s) Vault Provider 3.12 ### Terraform Configuration Files ```hcl terraform { required_providers...