You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Documenting a conversation had with rylagek about this:
Currently packer leaves the templates on the NEO_SPRN_LAN network, but with the static IP for when it get moved onto the range network.
This should be fine as when terraform does the networking the network should be changed to whatever it should be. It may be worth looking into if packer can handle that, but we don't think its possible or should be done for the following reasons:
Packer setting the network is outside its expected responsibilities. Terraform should be handling that
Packer giving the interface the static IP means it shouldn't matter what network gets plugged into that interface
It would take weird configuration with packer to give the shutdown signal, assign the static IP, and then "swap the cables". It's inelegant and almost certainly unnecessary
The text was updated successfully, but these errors were encountered:
Documenting a conversation had with rylagek about this:
Currently packer leaves the templates on the
NEO_SPRN_LAN
network, but with the static IP for when it get moved onto the range network.This should be fine as when terraform does the networking the network should be changed to whatever it should be. It may be worth looking into if packer can handle that, but we don't think its possible or should be done for the following reasons:
The text was updated successfully, but these errors were encountered: