-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First attempt at managing the nfcore org with pulumi #39
Conversation
Terraform Format and Style 🖌
|
Awesome! We also have I think the repo living here is the best pulumi cloud integration, things got weird when I tried to put the repo in the As for storing the credentials, we can just make a token and store it in pulumi cloud (once they approve our team for open source) then whenever a PR is merged to master it will run is the idea. Like I said on Gather town I think starting with Teams is a good way for us to safely get started, the worst case is that we accidentally delete a team and have to recreate it, not losing repos. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That all looks perfect to me, did it work?
Yep, it worked fine! Also private and public repos were created successfully, but we can keep them out of our pulumi stack at the beginning, as you suggested. Great to hear that we asked Pulumi to sponsor the project! Ping me once that is up and running I just noticed that we use sub-teams within the nf-core org, e.g. nf-core/infrastructure/ops, so I'll need to make the script iterative. |
BTW the Personal Access Token I created in the org needed the following permissions: Organization permissions:
Repository permissions:
Repository Access
|
I reworked the script to manage subteams. I also added explicit dependencies between resources, otherwise sometimes the resource that associates a team with a repo (or a team with a member) was failing because one of the two resources wasn't created yet. |
Awesome work! |
To clarify, I think we can add a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay I've gotten this to deploy with Pulumi cloud. Had to just add the secret manually and couldn't get it to work with Pulumi ESC for whatever reason.
Figured we can circle back around to that when we're comfortable using this for main nf-core org.
Hey Edmund, late for the hackaton, but I worked on issue #11 as we discussed.
This is a draft PR to manage the whole org with pulumi. It turns out it's easy enough once you get the feel of it.
I created a test organization
test-nfcore
and I used it to test the stack.I'm not sure how to move things forwards now, and how to e.g. store the secret org token in GH to run this automatically once the org structure is changed? Just by using a GHA that sets up the token by taking it from a GH secret every time?
I used this blogpost from pulumi to get started:
Which created a
Pulumi.dev.yaml
file (not commited in this PR). Any idea?