Add archived support and github_repository_vulnerability_alerts resource to repository_base

[Copilot]

GitHub has been unsetting/overriding two repository settings that Terraform wasn't explicitly managing. This PR adds explicit control over both.

Changes

archived field

• Added archived variable (default: false) to repository_base and wired it to the github_repository resource
• Propagated through public_repository, private_repository, internal_repository, and repository_set (as optional(bool))

github_repository_vulnerability_alerts resource

Added a dedicated github_repository_vulnerability_alerts resource controlled by the existing has_vulnerability_alerts variable:

resource "github_repository_vulnerability_alerts" "vulnerability_alerts" {
  count      = var.has_vulnerability_alerts ? 1 : 0
  repository = github_repository.repository.name
}

The has_vulnerability_alerts variable (default: true) now controls both the vulnerability_alerts attribute on the github_repository resource and whether the dedicated github_repository_vulnerability_alerts resource is created. This explicit resource prevents GitHub from silently disabling Dependabot alerts outside of Terraform's control.

Tests

Added assertions to repository_base/repository.tftest.hcl covering archived attribute correctness and github_repository_vulnerability_alerts resource creation.

[bzarboni1]

See comment to change repository.tf, then please add a conditional variable github_repository_vulnerability_alerts (True|False), with a default of false

[Copilot]

See comment to change repository.tf, then please add a conditional variable github_repository_vulnerability_alerts (True|False), with a default of false

Done in commit 974e341. Added github_repository_vulnerability_alerts (bool, default: false) to repository_base and propagated it through public_repository, private_repository, internal_repository, and repository_set. The resource is only created when this variable is true.