| 6 Apr 2022 |
 CRTified | Yes, that's a plan | 00:23:55 |
| CRTified | jhillyerd: although I'm heading to bed now, feel free to ping me. I did exactly the same migration from nixops to colmena+flakes | 00:40:19 |
|  David Arnold (blaggacao) joined the room. | 05:00:56 |
| 7 Apr 2022 |
|  Mark joined the room. | 08:17:39 |
| 8 Apr 2022 |
| CRTified | Sooo, building on the VM question: Did someone happen to stumble across a method of testing the whole deployment at once in VMs? Otherwise, I'll see whether I can build on the config.system.build.vm derivation and create a script that runs them in the same network | 15:13:14 |
 Zhaofeng Li | Not a real answer, but maybe you can take a look at the e2e tests that I have: https://github.com/zhaofengli/colmena/tree/main/integration-tests/apply | 18:10:53 |
| Zhaofeng Li | But yeah, I kind of want a nice setup to do something like that as well | 18:11:15 |
| CRTified | In reply to @zhaofeng:zhaofeng.li
But yeah, I kind of want a nice setup to do something like that as well I think it would generally be nice to have some place to collect useful snippets like the one I've posted in https://github.com/zhaofengli/colmena/issues/60 | 23:11:56 |
| 10 Apr 2022 |
 jhillyerd | I finished porting my old nixops config to a standard (not colmena) flake. Next I need to figure out secrets, as the janky system I was using previously doesn't work with flakes. Does the colmena secret deployment system work with the pure build environment of flakes? | 00:23:40 |
| CRTified | If you use the config.system.build.vm-path for the flakes, then there is no implementation for "uploading" the keys. I did not look into doing that myself, but might need to do soon | 00:30:33 |
| CRTified | * If you use e.g. the config.system.build.vm-path for the flakes, then there is no implementation for "uploading" the keys. I did not look into doing that myself, but might need to do soon | 00:30:44 |
| CRTified | So keys are only uploaded if you're using colmena, but not with the built flakes | 00:31:00 |
| David Arnold (blaggacao) | https://github.com/zhaofengli/colmena/pull/73 i wanted to quickly ping, to see if this is mergeable stuff. I think it's a neat ides to spin this further so that projecta can declare their local evaluator (which is great for lowering the magic) while still using upstream options and modules. | 00:37:14 |
| David Arnold (blaggacao) | I think the next improvement to this PR would be to make the evaluator configurable, so that it doesn't need to be patched into the binary. | 00:38:12 |
| David Arnold (blaggacao) | That way people can modify the colmena interface at will and make it work for their code / project structure. | 00:38:52 |
| David Arnold (blaggacao) | Instead of doing complicated transforms to match the expected interface. | 00:39:24 |
| jhillyerd | In reply to @schnecfk:ruhr-uni-bochum.de
So keys are only uploaded if you're using colmena, but not with the built flakes Thanks. I guess none of my services would start for local testing, so that's not really an option. 😕 I think I'll try agenix, that seems reasonable for homelab. | 00:40:59 |
| David Arnold (blaggacao) | * https://github.com/zhaofengli/colmena/pull/73 i wanted to quickly ping, to see if this is mergeable stuff. I think it's a neat idea to spin this further so that projecta can declare their local evaluator (which is great for lowering the magic) while still using upstream options and modules. | 00:41:00 |
| jhillyerd | Then again, I guess the host key would change for each VM... so maybe not. | 00:41:27 |
| 11 Apr 2022 |
| Zhaofeng Li | In reply to @blaggacao:matrix.org
https://github.com/zhaofengli/colmena/pull/73 i wanted to quickly ping, to see if this is mergeable stuff. I think it's a neat idea to spin this further so that projecta can declare their local evaluator (which is great for lowering the magic) while still using upstream options and modules. Sorry about the wait, and thing looks reasonable in the PR. I wanted to push 0.3 out (which has been stuck for quite a while) before merging, but got sidetracked by other stuff IRL. I'll hopefully get around to it later this week or next week. | 18:08:27 |
| David Arnold (blaggacao) | Oh great to hear! Yeah, I'm happy to get a little more involved with the codebase in the coming days / weeks. Planning on maybeMigrate 😂 | 23:24:16 |
| 12 Apr 2022 |
|  Linux Hackerman joined the room. | 18:47:42 |
| 18 Apr 2022 |
 aanderse | any way to specify multiple colmena outputs in a flake? basically i want a repo that houses n "hives" and tagging isn't enough to keep them separate | 20:34:28 |
| aanderse | maybe something like outputs = { ... }: { colmena-hive-1 = { ... }; colmena-hive-2 = { ... }; } then pass a flag tocolmena to tell it which one to process? | 20:36:20 |
| aanderse | or am i just thinking tags aren't my solution when really they are? | 20:36:53 |
 Buckley | Well, I guess that depends why you feel tags aren’t sufficient | 20:37:17 |
| Buckley | I think you can combine multiple tags to filter output down more, like @deployment1,@webservers will pick only the webservers which are also deployment1, but double check me there | 20:38:09 |
| Buckley | Then multiple deployments… | 20:38:26 |
| aanderse | defaults apply to all machines regardless of tags, i don't want to accidentally reference a machine in a different tag via nodes, i want to grab all attributes from all machines in a tag | 20:38:45 |
| Linux Hackerman | In reply to @buckley310:matrix.org
I think you can combine multiple tags to filter output down more, like @deployment1,@webservers will pick only the webservers which are also deployment1, but double check me there nope, that's all @deployment1 and all @webservers | 20:39:23 |
