terraform-provider-github icon indicating copy to clipboard operation
terraform-provider-github copied to clipboard

Terraform GitHub provider

Results 439 terraform-provider-github issues
Sort by recently updated
recently updated
newest added

Update documentation for github_team_members resource: - Update details of "members" property. In fact it is required, not optional - Fix small typo Closes: #1105

Hi there, we are experinsing issue when try to remove resource `teams_permissions` for team which has on Enterprise org level `security manager role`. ### Terraform Version Terraform v1.0.11 - integrations/github...

bug
documentation
r/team_repository

### Terraform Version ``` terraform version Terraform v1.1.2 on darwin_amd64 + provider registry.terraform.io/hashicorp/aws v3.70.0 + provider registry.terraform.io/integrations/github v4.19.1 ``` (Also tested with v4.19.0) ### Affected Resource(s) - `github_repository_environment` ### Terraform...

- Refactor out branches attribute from `resource_github_repository` and `data_source_github_repository` - Introduce a new data_source called `data_source_github_repository_branches` that returns branches instead. `Rationale:` I believe branches shouldn't belong to the attributes of...

Hi there, ### Terraform Version 4.27.0 ### Affected Resource(s) - resource_github_team_repository ### Expected Behavior Things keep working as in

Adds support for defaulting to using PR titles for squash merge commit messages ([Github announcement](https://github.blog/changelog/2022-05-11-default-to-pr-titles-for-squash-merge-commit-messages/)) Related: https://github.com/google/go-github/pull/2390 Closes #1150

Support for GitHub Advanced Security and Secret Scanning. The current repository resource does not support the parameter: `security_and_analysis` which is used to enable both GHAS and secret scanning on a...

### Terraform Version Terraform 0.13.6 ### Affected Resource(s) - github_actions_public_key ### Terraform Configuration Files ```hcl provider "github" { token = var.github_token organization = "buffalogrid" } data "github_actions_public_key" "repo_public_key" { repository...

bug
d/actions_public_key

Updating the documentation to reflect current behavior - if members is meant to be optional I can open an Issue instead, but either way the documentation does not match behavior...

We use teams as codeowners for required reviews on many of our repositories and would like to take advantage of the code review settings for teams: https://docs.github.com/en/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team#about-auto-assignment