works fine, but the password is not treated as a sensitive field by the provider and the plan shows the raw password when outputted in the terminal or pipeline.
This "feature" makes it almost impossible to use the provider in a setup where you want to generate a password, store it in a vault (e.g. key vault) to ensure that it is kept secret.
I hope you could change this soon in a forthcoming version, I could also provide you with a PR if that would speed things up.
Hi
I have recently discovered that creating a custom user in the following way:
works fine, but the password is not treated as a sensitive field by the provider and the plan shows the raw password when outputted in the terminal or pipeline.
This "feature" makes it almost impossible to use the provider in a setup where you want to generate a password, store it in a vault (e.g. key vault) to ensure that it is kept secret.
I hope you could change this soon in a forthcoming version, I could also provide you with a PR if that would speed things up.
Kind Regards Jakub