supergit auth | Dagger | Page 1

opaque moth Dec 19, 2023, 10:29 PM

#

definitely in scope 🙂

#

My goal is to offer be a 100% feature-complete git API 🙂 (one day)

#

a very good question

turbid arch Dec 20, 2023, 2:57 PM

#

I got this to work using the principle of most jenkyness, just to get it working, I am almost afraid to paste the code snippet because its a massive security risk 👼

In brighter news I have a "real world" pipeline that is a module that builds a static site, uses another module to inject some additional content into that site, and deploys to github pages using git (one day using supergit!)

It was also directly translated from a "classic dagger" program, so I finally have a real world side-by side comparison.

Feels great, except for the hacky auth thing 😂

opaque moth Dec 20, 2023, 3:00 PM

#

Did you use the Secret type? You can pass those from the CLI

#

The slight inconvenience is that you have to pass everything explicitly, since Dagger Functions can't access your machine's environment variables or filesystem implicitly

turbid arch Dec 20, 2023, 3:15 PM

#

I will iterate on this a bit - I got this working by not using secrets basically - I have a deploy key in this repo (its a private repo) and the module will never be published, so I just copied the file in.

opaque moth Dec 20, 2023, 3:16 PM

#

Yeah definitely a hack 😛 That secret will stay in your cache

#

But should not be hard to upgrade to a secret, they're pretty easy

turbid arch Dec 20, 2023, 3:17 PM

#

Yeah I am not proud of the implementation, but getting something working gives me some fuel to keep hacking haha!

#supergit auth