| 24 Sep 2021 |
 lukegb (he/him) | 1026 is also cool | 23:40:19 |
 @grahamc:nixos.org | Sufficient? | 23:40:46 |
| 25 Sep 2021 |
| @grahamc:nixos.org | Also, make sure to reply on the PR if you like it / don't like it / tried it :). | 00:03:03 |
| 27 Sep 2021 |
| @grahamc:nixos.org | just re-upping, das_j and lukegb (he/him) does https://github.com/NixOS/hydra/pull/1026 implement what you need? | 14:40:26 |
| lukegb (he/him) | hey, sorry, I hadn't got around to taking a look yet | 14:41:17 |
| @grahamc:nixos.org | no worries | 14:41:37 |
| 28 Sep 2021 |
 mbprtpmnr | Another question, is there a way to have something like, one hydra master in DE and two hydra slaves in US and to have some loadbalancer in between? | 08:37:21 |
 das_j | grahamc (he/him): Maybe my knowledge of the framework is lacking here, but does $self->status_ok ever return a non-200 code? | 10:06:00 |
| das_j | I'm asking because you specify 404 as a possible response code | 10:06:30 |
| @grahamc:nixos.org | This sub never gets called if the build doesn’t exist, see the Chained thing? It calls that named sub first, which sometimes will issue a 404 | 11:25:16 |
| das_j | Oops, right. Thanks for that clarification | 11:48:27 |
|  marcecoll joined the room. | 12:52:30 |
 Mic92 | @grahamc: your hydra terraform provider works great: https://github.com/Mic92/dotfiles/blob/master/nixos/eve/modules/hydra/jobs.tf | 19:59:03 |
| @grahamc:nixos.org | Cool, I’m glad to hear it! | 20:06:32 |
| @grahamc:nixos.org | I want to make a vault provider too. | 20:07:09 |
| @grahamc:nixos.org | cc cole-h ^ | 21:05:33 |
| @grahamc:nixos.org | also I think data providers for jobsets/jobs/aggregate jobs would be interesting | 21:16:22 |
| 29 Sep 2021 |
| Mic92 | @grahamc: I am still thinking about just serializing json in our nixpkgs hydra module and running the terraform provider in service. I think eelco would also prefer that for the nixos foundation. | 09:31:48 |
| Mic92 | * @grahamc: I am still thinking about just serializing json in our nixpkgs hydra module and running the terraform provider in a service. I think eelco would also prefer that for the nixos foundation. | 09:32:25 |
| Mic92 | You already put in the effort to fully document every option... | 09:32:55 |
| @grahamc:nixos.org | I don't understand what you mean | 12:21:49 |
| @grahamc:nixos.org | but I don't think this accomplishes my goal of letting people adjust jobsets without doing a full deploy to hydra | 12:22:11 |
| Mic92 | @grahamc: I guess it does not. My goal was to have nixos using the terraform provider. | 12:34:20 |
 ajs124 | NixOS could just use the declarative jobsets | 12:37:15 |
| Mic92 | one can also upload them via curl, but terraform looks cleaner to me | 12:40:10 |
| @grahamc:nixos.org | Right. I already do use the terraform provider for when people ask me to make changes to hydra.nixos.org, anyway | 13:19:02 |
| Mic92 | After using the terraform provider for a bit longer, I also prefer it over integrating something into nix. | 19:43:01 |
| 30 Sep 2021 |
|  Robby O'Connor joined the room. | 01:16:13 |
|  matrixforever joined the room. | 02:16:16 |
| matrixforever left the room. | 04:36:09 |
