-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove secret crypted by terraform on junos_system_tacplus_server #688
Comments
Hi 👋 The provider doesn't encrypt plain text secrets, but Junos device encrypts plain text secrets with an obfuscation algorithm, which is easily reversible. With the current version of the provider, if you add an encrypted secret to the attribute in the config, it will be correctly added. Still, a refresh of the resource will detect a drift between the attribute in the config and the attribute in the state. Passwords of system users (root and other user) are encrypted with a different algorithm which is not reversible, so there is two options on the corresponding resources ( So for your needs, I'll take care of adding an option to the provider to disable automatic decoding of secrets. So you will be able to add encrypted secrets without causing an attribute drift. |
to disable decoding secret hashes by Junos device when reading resource data Fix #688
to disable decoding secret hashes by Junos device when reading resource data Fix #688
to disable decoding secret hashes by Junos device when reading resource data Fix #688
to disable decoding secret $9$ hashes by Junos device when reading resource data Fix #688
hello,
on resource "junos_system_tacplus_server" there is the variable "secret (Optional, String, Sensitive)" that has to be plain text password in order to be crypted by terraform. Because i dont wanna have the clear password in the configuration code but directly the crypted one, is it possible to add an option to choose it we want it converted by terraform or not ?
like you do for resource "junos_system_root_authentication with
Thanks in advance
The text was updated successfully, but these errors were encountered: