| 20 Oct 2021 |
 @grahamc:nixos.org | I thought about migrating all the opens to use parens and got lazy ... :) | 16:52:58 |
 das_j | understandable | 17:10:37 |
| @grahamc:nixos.org | I made them all open's use parens | 17:16:22 |
| @grahamc:nixos.org | I'm going to smash the merge button since nothing material has changed since the reviews, except the parens | 17:16:36 |
| @grahamc:nixos.org | thank you for the reviews :) | 17:16:45 |
| @grahamc:nixos.org | data "hydra_job" "system" {
project = "app"
jobset = "production"
job = "webserver"
}
resource "aws_instance" "web" {
# ...
provisioner "remote-exec" {
inline = [
"nix-env --profile /nix/var/nix/profiles/system --set '${data.hydra_job.system.outputs.out.path}'",
"/nix/var/nix/profiles/system/bin/switch-to-configuration switch",
]
}
}
| 19:07:38 |
| @grahamc:nixos.org | * data "hydra_job" "system" {
project = "app"
jobset = "production"
job = "webserver"
}
resource "aws_instance" "web" {
# ...
provisioner "remote-exec" {
inline = [
"nix-env --profile /nix/var/nix/profiles/system --set '${data.hydra_job.system.outputs.out.path}'",
"/nix/var/nix/profiles/system/bin/switch-to-configuration switch",
]
}
}
| 19:07:41 |
| @grahamc:nixos.org | * data "hydra_job" "system" {
project = "app"
jobset = "production"
job = "webserver"
}
resource "aws_instance" "web" {
# ...
provisioner "remote-exec" {
inline = [
"nix-env --profile /nix/var/nix/profiles/system --set '${data.hydra_job.system.outputs.out.path}'",
"/nix/var/nix/profiles/system/bin/switch-to-configuration switch",
]
}
}
| 19:07:51 |
| @grahamc:nixos.org | just something I'm noodling on | 19:09:53 |
| das_j | is this some hail alternative? | 19:10:03 |
| @grahamc:nixos.org | no | 19:10:10 |
| @grahamc:nixos.org | but you could use this to boot a NixOS AMI and get its very first config deployed which is set up to pull from hydra on a regular baslis | 19:10:34 |
| @grahamc:nixos.org | * but you could use this to boot a NixOS AMI and get its very first config deployed which is set up to pull from hydra on a regular basis | 19:10:36 |
| das_j | ah that's just an initial provisioning thing | 19:10:56 |
| @grahamc:nixos.org | yeah | 19:11:00 |
| @grahamc:nixos.org | or maybe you do immutable deployments and make new instances for every deployment | 19:11:16 |
| das_j | btw, is it just me or was the code on your blog pretty similiar to the stuff I sent to you a couple of months back? :D | 19:11:19 |
| das_j | In reply to @grahamc:nixos.org
or maybe you do immutable deployments and make new instances for every deployment that's a nice icea | 19:11:28 |
| das_j | In reply to @grahamc:nixos.org
or maybe you do immutable deployments and make new instances for every deployment * that's a nice idea | 19:11:30 |
| @grahamc:nixos.org | I mean ... it is similar ... :P | 19:11:58 |
| @grahamc:nixos.org | there are only so many ways to do it! | 19:12:16 |
| @grahamc:nixos.org | :joy: | 19:12:20 |
| das_j | you could do it in haskell for no reason :D | 19:13:17 |
| @grahamc:nixos.org | I could see justifiable reasons | 19:13:28 |
 tomberek | I've used the "remote-exec" as a deployment alternative before. With lifecycle options it's effective even as a continuous provisioning. Pointing to hydra output via Terraform is nice. | 19:14:01 |
| @grahamc:nixos.org | like if you're putting a lot of work in to observability around it | 19:14:03 |
| @grahamc:nixos.org | https://github.com/DeterminateSystems/terraform-provider-hydra/issues/72 | 19:15:23 |
 cransom | In reply to @grahamc:nixos.org
data "hydra_job" "system" {
project = "app"
jobset = "production"
job = "webserver"
}
resource "aws_instance" "web" {
# ...
provisioner "remote-exec" {
inline = [
"nix-env --profile /nix/var/nix/profiles/system --set '${data.hydra_job.system.outputs.out.path}'",
"/nix/var/nix/profiles/system/bin/switch-to-configuration switch",
]
}
}
that is smooth. we do the ami baking, but the next speed hack, i was contemplating was for the deploy to upload a user-data for cloud-init that does a nix-store -r <system path>; <system path>/bin/switch-to-configuration switch and then either launch or reboot machines. | 20:17:32 |
|  hpfr joined the room. | 21:12:52 |
| hpfr | maybe this is a better place to ask?
https://nixos.org/channels/nixos-unstable is behind https://status.nixos.org, which I didn't even think was possible. shouldn't the status page wait until the channel itself actually updates?
| 21:13:21 |
