github_organization_role_team_assignment vs github_organization_role_team

[d-m]

What is the difference between these two resources?

• github_organization_role_team_assignment "This resource manages relationships between teams and organization roles in your GitHub organization."
• github_organization_role_team "Manage an association between an organization role and a team."

[pascal-hofmann]

It's just a duplicate. They really do the exact same thing. 🙈

See #2322 (comment)

[ChaninduImanjith]

They are effectively duplicates and manage the same relationship: assigning an organization role to a GitHub team.

The main practical difference now is that `github_organization_role_team_assignment` is the older resource, while `github_organization_role_team` is the resource to prefer going forward.

For new Terraform configurations I would use:

```hcl
resource "github_organization_role_team" "example" {
  role_id   = 1234
  team_slug = "example-team"
}

Both resources use the same underlying concept: a role_id associated with a team_slug.

So unless you need to maintain an existing configuration that already uses github_organization_role_team_assignment, I would choose github_organization_role_team for new code.