Open Shocktrooper opened 2 months ago
1.8.3
4.3.0
1.17.2
vault_aws_auth_backend_role
Resource updates should happen
Terraform says it will apply updates and after a successfully reported update the downstream configuration is not made and subsequent plans show the same change that was never successfully made
No response
resource "vault_aws_auth_backend_role" "test" { backend = vault_auth_backend.backend.path role = "test" auth_type = "ec2" allow_instance_migration = true bound_account_ids = ["12345"] bound_vpc_ids = ["vpc-12345"] bound_subnet_ids = ["subnet-12345"] token_ttl = 60 token_max_ttl = 120 token_policies = ["default"] }
resource "vault_aws_auth_backend_role" "test" { backend = vault_auth_backend.backend.path role = "test" auth_type = "ec2" allow_instance_migration = true # bound_account_ids = ["12345"] # bound_vpc_ids = ["vpc-12345"] # bound_subnet_ids = ["subnet-12345"] token_ttl = 60 token_max_ttl = 120 token_policies = ["default"] }
bound
https://github.com/hashicorp/terraform-provider-vault/issues/1773
No
Terraform Core Version
1.8.3
Terraform Vault Provider Version
4.3.0
Vault Server Version
1.17.2
Affected Resource(s)
vault_aws_auth_backend_role
Expected Behavior
Resource updates should happen
Actual Behavior
Terraform says it will apply updates and after a successfully reported update the downstream configuration is not made and subsequent plans show the same change that was never successfully made
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
vault_aws_auth_backend_role
resource to your liking and apply the initial configurationbound
attributes and make a subsequent applyDebug Output
No response
Panic Output
No response
Important Factoids
No response
References
https://github.com/hashicorp/terraform-provider-vault/issues/1773
Would you like to implement a fix?
No