samueldr changed the topic of #nixos-infra to: NixOS infrastructure | logs:
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-infra
<gchristensen> niksnut: how about here?
<niksnut> or nixos-foundation
<gchristensen> niksnut: so the long and short of it is we have a bunch of images that we need to build and send to external parties like AWS and Packet, and then some that we do a pretty bad job of maintaining which I wish we did a good job of
<gchristensen> those are like: Azure and GCP, and now we have community people who want to contribute more. I have a list now, actually: DigitalOcean, OVH, the Windows app store
<gchristensen> Hydra is a "fine" way to do this, but they don't really need to built often and they require some impure steps in the build and "release" process.
<gchristensen> I'd like there to be a a way for community members to add more, debug builds, and easily participate in supporting targets like these. right now, the process for AWS for example is not great and requires a lot of work from somebody with SSH access to the foundation's servers, and I'd like there to be something a bit easier, visible, transparent
<gchristensen> these sorts of "impure" things, IMO, also fit in nicely with things like channel update jobs, which I'd also like to make public, but is a different proverbial can of worms
<aminechikhaoui> AWS process just needs AWS credentials btw not necessarily ssh access to bastion. But I agree it's not transparent and it's very manual
<gchristensen> yeah
<gchristensen> I think it is really valuable to support people who want it to work in places, and doing it officially helps everybody (us, them, users)