It also solves a problem where multiple deployments to distinct private networks fight over the key for the same ip that occurs in both.
nixops import --include-keys-like functionality doesn't seem to be included.
Prevously, you'd
create a deployment
upload the state
download the deployment state on a fresh machine (eg colleague)
nixops ssh doesn't know the keys
non-interactive deployments fail
With this pr, we don't have to rely on user configuration to include
known_hosts entries for the deployments.
It makes nixops import --include-keys unnecessary, unless you
use those entries outside of nixops.
Since recently we can get our deployment state from remote storage
backends, but we didn't have a way to get configure the known_hosts
yet. This is now largely unnecessary.
This functionality requires some cooperation from the plugins. For
instance, here's what ec2 needs to do: (pun intended)
Solves one of the problems from https://github.com/NixOS/nixops/pull/1264#issuecomment-889884626
It also solves a problem where multiple deployments to distinct private networks fight over the key for the same ip that occurs in both.
Prevously, you'd
With this pr, we don't have to rely on user configuration to include known_hosts entries for the deployments.
It makes
nixops import --include-keys
unnecessary, unless you use those entries outside of nixops.Since recently we can get our deployment state from remote storage backends, but we didn't have a way to get configure the known_hosts yet. This is now largely unnecessary.
This functionality requires some cooperation from the plugins. For instance, here's what ec2 needs to do: (pun intended)
(https://github.com/NixOS/nixops-aws/pull/141)