-
Notifications
You must be signed in to change notification settings - Fork 0
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
Formalize GitHub configurations for pathogen repos #25
Comments
Another one I can think of is labels (mentioned by @tsibley). Both that and "automatically delete head branches" seem applicable to not just pathogen repos but all repos under @nextstrain. Is there a simple way to specify all repos instead of listing every single repo in |
Ah, thanks! I vaguely remember this coming up before but couldn't find the thread. At least github_issue_labels looks like a resource that applied across the entire GitHub organization. From what I can see, the github_repository resource is only applied per repo... |
You bring in the repos dynamically as a Terraform data source, e.g. here with data "github_repositories" "nextstrain" {
query = "org:nextstrain"
} and then apply the per-repo resource (e.g. resource "github_issue_labels" "nextstrain" {
for_each = data.github_repositories.nextstrain.full_names
repository = each.key
…
} A similar pattern is already used for getting the existing topics for repos in |
It's per-repo, see the arguments and the required |
Ah, thanks for the tip + correction @tsibley! So seems pretty do-able! |
Context
Prompted by nextstrain/yellow-fever#7 (comment) and nextstrain/rabies#2 (comment).
Description
We should decide on a default set of GitHub configs that can be formalized in Terraform and applied across pathogen repos that we track in infra. We already add GitHub topic labels through Terraform, seems like a good place to add other configs.
Decide on default configs
Refer to available
github_repository
arguments.The text was updated successfully, but these errors were encountered: