| 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 |
| Buckley | Oh never mind then :/ | 20:39:33 |
| Buckley | Might be remembering another tool, I’ve never used multi tags on colmena | 20:39:55 |
| aanderse | i guess i just put my defaults into a separate file and include it for each separate deployment, etc... | 20:41:15 |
| Buckley | You can have one flake that has all your hosts in it, then you can have little hive files that just import specific hosts from your flake | 20:43:31 |
| Buckley | stub hives | 20:43:44 |
| aanderse | Buckley: that sounds ideal | 20:45:14 |
| aanderse | not that i read much into it, but i thought colmena depended on the output called colmena | 20:45:30 |
| Linux Hackerman | Being able to specify an "installable" to use as the hive would be nicer though. | 20:45:39 |
| aanderse | so how does my flake.nix look in your scenario? | 20:45:42 |
| aanderse | Linux Hackerman: yes, that | 20:45:52 |
| Buckley | Probably just use the non-flake hive files in a folder, then they make calls into the top level flake and just select the hosts they want. Although then that would mess with the nodes input… not sure if that’s an issue | 20:47:20 |
| aanderse | definitely need nodes | 20:47:40 |
| Buckley | That’s what I used to do when I used morph anyway | 20:47:44 |
| Buckley | Well then it’ll be a little more involved | 20:48:19 |
| Buckley | You could always procedurally generate your tags… so like produce a tag deploy1_webservers for machines which are both deployment1 and webservers | 20:49:27 |
| Buckley | Not sure exactly what that code would look like right now | 20:49:43 |
| Linux Hackerman | This all sounds like not-so-great workarounds for a problem that would be best solved by adding the feature to colmena. | 20:50:02 |
| Buckley | That would be the over engineered way | 20:50:04 |
| aanderse | ok cool | 20:50:30 |
