I have scenario where I’d like to create an arbitrary number of “vault_database_secret_backend_connection” resources, where each one may refer to a different database configuration.
My original idea was to use the mysql provider to provision an admin user for each one, pass the created user to vault and rotate those credentials.
I couldn’t go this way due to the fact that the number of provider configurations can’t be determined in advance, so I can’t use the “alias” trick.
I was able to do what I need using a local-exec provisioner, calling mysql directly. This, however, made me think: is this a valid use case for the “for_each” construct ? If so, is there any plans to add “for_each” support to providers ?