| Commit message (Collapse) | Author | Age |
|
|
|
| |
27016659046a8f8e7b4fd61ecbceaf9f5e306258 broke this.
|
|
|
|
|
|
| |
Since we're already fetching one datum, we may as well fetch the
others needed by fetch-ec2-data. This also eliminates the dependency
on wget.
|
| |
|
|
|
|
| |
Also, don't barf if there is no DSA key.
|
| |
|
| |
|
|
|
|
| |
https://github.com/NixOS/nixops/issues/267
|
| |
|
|
|
|
|
|
| |
ec2.metadata = true, as the existing (default) blackhole will not be cleared.
(cherry picked from commit ccf672ca6b055e5e862e45b65d122754c16cf7d1)
|
|
|
|
|
| |
This service only needs to run once on system startup, so it doesn't
need to be restarted by switch-to-configuration.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
curl does not retry if it is unable to connect to the metadata server.
For some reason, when creating a new AMI with a recent nixpkgs, the
metadata server would not be available when fetch-ec2-data ran. Switching
to wget that can retry even on TCP connection errors solved this problem.
I also made the fetch-ec2-data depend on ip-up.target, to get it to start
a bit later.
|
|
|
|
|
|
|
|
| |
Using pkgs.lib on the spine of module evaluation is problematic
because the pkgs argument depends on the result of module
evaluation. To prevent an infinite recursion, pkgs and some of the
modules are evaluated twice, which is inefficient. Using ‘with lib’
prevents this problem.
|
| |
|
|
|