Re. Pulumi GitHub provider, I saw the excellent 20...
# getting-started
s
Re. Pulumi GitHub provider, I saw the excellent 2022 blog by @shy-arm-32391 and I was wondering if a follow-up had been written. In particular, would there be any new advice, not found in the blog, for a GitHub org getting started with pulumi today?
s
Iā€™m not aware of any follow-up, but perhaps @shy-arm-32391 will weigh in directly! šŸ™‚
s
hi friends! This provider has been fairly stable in terms of features, and so has our internal use of the provider (which focuses mostly on repo permisson management and org structure). We've not had to make significant updates to our handling of GitHub IaC resources. I did poke and I see that upstream is [releasing a new major version soon](https://github.com/integrations/terraform-provider-github/releases/tag/v6.0.0-beta), which we will have available shortly after.
s
Thanks for the update. Do you use a GitHub provider to create repos and/or manage branch protection?
s
I think we use it for branch protection somewhere, but not to create repos.
Creating repos is not something we want to require a layer of abstraction for heh šŸ˜…
s
I think something like Backstage scaffolding might be useful for creating repos. But I'm still looking for a good way to manage changes to repo state, such privacy and branch protection rules.
s
Yeah! I think those are good use cases here. One thing to consider is that you'll always have folks with admin privileges going through and making manual changes via the UI, which may result in unexpected diffs in your pulumi state. There's ways to handle this, but worth thinking about a strategy first.