Ben Ash
Ben Ash
Related fix to the Vault Provider fix which makes `password_policy` conflict with `length` and `formatter` https://github.com/hashicorp/terraform-provider-vault/pull/1557
@faseyiks you may want to try a `terraform import` if you want to bring a non-terraform managed Vault resource into your state. See https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/ad_secret_backend#import for more details.
Fixed in #1607 and #1618
Fixed in #1618
I am not sure this is related to this issue but I think that that the values for `kubernetes_ca_cert` and `token_reviewer_jwt` may be reversed in your example resource.
Ah, no worries. Thanks for the clarification! I do see a potential culprit in the code. Going to do some preliminary testing to confirm.
I wonder if you wouldn't mind describing your setup/workflow a bit? For example: - How many modules do you have for each vault `provider{}` block? - How many Vault server...
Closed with #1146
I wonder if adding a new `vault_transit_secret_backend_import_key` resource might be a better alternative to updating the current resource. That approach seems to align with the API: https://www.vaultproject.io/api-docs/secret/transit#import-key. Thoughts?
@vinay-gopalan would the work you are doing with dedicated kvv2 resources help @maxb out here?