Has anyone compared pulumi-github with the GitHub ...
# general
s
Has anyone compared pulumi-github with the GitHub Provider for terraform? In my experience, the terraform provider is fiddly, incomplete, and not yet ready for automation - at least not for all the GitHub infra I'd like to manage. Is pulumi-github substantially better? (Even though I assume it, like the tf provider, both leverage the same golang API?) OTOH, I've found very few (2?) reports from anyone using IaC to mange GitHub itself, so I wonder if I'm looking at the problem in the wrong way. Like, maybe what I need is an IDP, Backstage scaffolding, or the like. Or maybe I should separate user management from repo management, and use different tools for each? (Which are generally used by different groups of users) Any pointers appreciated.
w
The
pulumi-github
provider is a "bridged" provider, so depending on your terraform struggles you might hit similar obstacles with the pulumi provider.
Having said that, we use it internally for repo membership and permissions, I've no big complaints.
Auth is a lot easier if you use Pulumi deployments for it though, because Github authentication is handled by the Pulumi Github app.
Generating Github authentication tokens manually is a pest, and I've never found a decent way of scripting it.
s
Thanks. There was a helpful article about Pulumi's use written in 2022, too.