-
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
feat: create envs for managed repos using terraform #44
Conversation
Files changed: M terraform/resources-environments.tf
Terraform plan in terraform Plan: 2 to add, 0 to change, 0 to destroy.Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# github_repository_environment.pypi["django-tasks-scheduler"] will be created
+ resource "github_repository_environment" "pypi" {
+ can_admins_bypass = true
+ environment = "pypi"
+ id = (known after apply)
+ prevent_self_review = false
+ repository = "django-tasks-scheduler"
+ reviewers {
+ teams = [
+ 10707221,
]
}
}
# github_repository_environment.testpypi["django-tasks-scheduler"] will be created
+ resource "github_repository_environment" "testpypi" {
+ can_admins_bypass = true
+ environment = "testpypi"
+ id = (known after apply)
+ prevent_self_review = false
+ repository = "django-tasks-scheduler"
}
Plan: 2 to add, 0 to change, 0 to destroy. 📝 Plan generated in Plan org changes and list them in a PR #84 |
Files changed: M terraform/resources-environments.tf
This includes a step to walk through the release process with the maintainer as a way of onboarding them.
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.
Thanks for adding this in! Always great to simplify a process.
When importing a new repo - it will automatically create pypi and testpypi environments with the relevant rules.