This message was deleted.
s
This message was deleted.
👍 3
🎉 1
b
let us know how we can help
1
❤️ 1
a
Will do 🙂
s
We have a GitLab provider if you want to get fancy and define any GitLab resources using Pulumi as well: https://www.pulumi.com/registry/packages/gitlab/api-docs/
👍 1
a
I'll definitely check it out now. Maybe that's the first one I was playing with 2 nights ago. Thank you!
oh for managing Gitlab, got it. I'll bookmark it. We might need it for sure. Right now, I'm focused on application load balancers, ec2, s3, WAF, etc
s
I advise you to not put repos under IaC tho - too easy to delete them and potentially lose data. Or at least be very careful when doing so. We do not put our repos under IaC at Pulumi, but we do control stuff like repo access with Pulumi.
a
Are you saying that our developer applications and tooling should not be deployed by Pulumi? It's because some of our toolings or tools are in repos and are built either in Jenkins or in Gitlab. So far, we have never encountered an issue yet. It's been 5+ years now
Like for example, some s3 buckets are deployed by Terraform and its configurations are saved in a git repo
We do not put our repos under IaC
I think we are doing it the other way around. We put IaC in repos in self managed gitlab
s
I'm talking about managing your organization's git repos as Pulumi resources. For example. the GitLab provider has a Repository resource that allows you to create/update/destroy git repositories in GitLab. At Pulumi, we still create repositories manually in the GitHub UI, but we still manage permissions to those repos (like which teams can submit or approve PRs) via Pulumi. (I think I inadvertently and unnecessarily confused you here - my apologies.)
a
No worries. 🙂 Thank you