Closed StevenHolm closed 1 month ago
+1
+1
As the configuration of a BGP password using a unencrypted password returns the encrypted version of the password is it required to add the following lifecycle statement to the nxos_bgp_peer resource.
lifecycle { ignore_changes = [ password_type ] }
This instructs Terraform to ignore that the desired value is not identical to the one returned by the Nexus device
Usecase
I've been looking into deploying some nexus switching using terraform as the orchestration tool. I found the following resources were missing from the available resources
Ability to set local as on bgp peer
Ability to set BFD, TTL (eBGP multihop) and password og bgp peer
The password seems to be returned in the encrypted state - is there a way to encrypt the password prior to deploying it? and then in turn deploy it using passwdType 3?
Ability to set passive-interface default and bfd on ospf instance
General security, ability to change the default state of physical ports