You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the support for credential_type and credential_config configuration in vault_database_secret_backend_static_role and vault_database_secret_backend_role is patchy and challenging. In a multi-namespace setting when you want to support multiple credential types using the same module, this is even rather impossible
Affected Resource(s) and/or Data Source(s)
vault_database_secret_backend_static_role, and
vault_database_secret_backend_role`
Potential Terraform Configuration
(I realise some of the attributes are rather verbose and too expansive for most use cases (especially the client_certificates but these are all the possible attributes that could possibly be configured to generate a client certificate)
faseyiks
changed the title
[Enhancement]:
Support database dynamic credential_type & credential_config
Jul 29, 2024
faseyiks
changed the title
Support database dynamic credential_type & credential_config
Support database dynamic credential_type & credential_config block
Jul 29, 2024
Description
This request further expands on
#2244
Currently the support for credential_type and credential_config configuration in
vault_database_secret_backend_static_role
andvault_database_secret_backend_role
is patchy and challenging. In a multi-namespace setting when you want to support multiple credential types using the same module, this is even rather impossibleAffected Resource(s) and/or Data Source(s)
vault_database_secret_backend_static_role, and
vault_database_secret_backend_role`
Potential Terraform Configuration
(I realise some of the attributes are rather verbose and too expansive for most use cases (especially the
client_certificates
but these are all the possible attributes that could possibly be configured to generate a client certificate)References
No response
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: