Open chrs-myrs opened 2 years ago
My bad - some time ago, this was removed in one refactoring while docs were not removed: it is commit 443494e32832ee004eabd06e1f3535ed7c0220d1 - it merged handling of different passwords.
Is it still necessary for you?
I've recently hit this same issue. I don't need the feature but it would be worth updating the documentation to reflect the refactor :)
@petoju I am using the pgp_key attribute as this makes sure only the owner of the Keybase account can actually decrypt the passwords.
First I was using the "winebarrel/mysql" provider for this, but they refer to this repository since they don't maintain it anymore. Is it possible to add support for the pgp_key again? Or maybe there's another way to accomplish this?
@OurFriendIrony you're right, I will remove it from docs.
@JoeyHoutenbos It may return, but I feel like that is solving an issue on incorrect level. Maybe this provider would be willing to add pgp_encrypt? That would solve your situation: https://registry.terraform.io/providers/ekristen/pgp/latest/docs/data-sources/pgp_decrypt
@petoju I am using the pgp _key attribute also and my question Is it would be possible to add again ? It will be great ¡¡ I was working with "winebarrel/mysql" and we have all pgp files added to the terraform. Thanks.
Terraform Version
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Debug Output
https://gist.github.com/chrs-myrs/f70647ce9a7ed35c37747ce721d65aa6
Panic Output
N/A
Expected Behavior
The user should be assigned a password which is then PGP decrypted.
Actual Behavior
Terraform rejects the documented attribute, even though it is required on this resource type (https://registry.terraform.io/providers/petoju/mysql/latest/docs/resources/user_password).
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
Tunnelling into mysql via an ssh bastion