John-Michael Faircloth

@aselmi I am sorry you are having trouble. I tried the following and I am unable to reproduce the issue: ``` resource "vault_auth_backend" "ldap" { path = "at-work" type =...

@symmediabruell Can this be closed or are there improvements that you would like to see here? Thanks

@rv-harsha Hello! I am sorry you are having trouble. Can you try using `role`? ```diff -name = vault_azure_auth_backend_role.this.role_id +name = vault_azure_auth_backend_role.this.role ``` https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/azure_auth_backend_role#role

The role `name` is the role's unique identifier. I am not aware of a `role_id` field returned by the azure auth plugin.

@nfi-hashicorp Hello! The [vault_policy](https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/policy) resource should allow you to copy-paste the hcl directly. Does that work for your use case?

@nfi-hashicorp Thanks for the clarification. In that case, I think you could write the vault policy as a separate file and then use the [file function](https://developer.hashicorp.com/terraform/language/functions/file)? Something like: ```hcl resource...

@sebastienbonami Thanks for reporting! I don't have the context as to why the deprecation was announced. We are going to reevaluate this deprecation. Related to https://github.com/hashicorp/terraform-provider-vault/issues/2130

Thanks @arpanrec for reporting! If I am understanding correctly there are 2 options 1. Make `auth_login` and `auth_login_cert` not mutually exclusive 2. Do not remove `client_auth` from any future versions...

Thanks! Option 1 was hypothetical. I have not investigated if there are cases where it could make sense. I will discuss this issue with my team. Thanks!

@tmatilai FYI, I opened a PR which will supersede this PR.