[feat]: Enterprise Settings

[HariSekhon]

Relates to: #1200

As a user of the github terraform provider I need to be able to use the current Enterprise settings APIs avaiable in go-github-v67 so that I can properly manage my enterprise needs.

Details

✅ Read-only workflow permissions by default - Available via DefaultWorkflowPermissionEnterprise
✅ Contributor approval permissions - Available via ContributorApprovalPermissions
✅ Advanced Security - Available via EnterpriseSecurityAnalysisSettings
✅ Secret scanning - Available via EnableDisableSecurityFeature
✅ Secret scanning push protection - Available via EnableDisableSecurityFeature
✅ Self-hosted runner permissions - Available via SelfHostRunnerPermissionsEnterprise

Eventually we will need to implement the following as documented in issue #2851

[HariSekhon]

GitHub Enterprise support have confirmed the Rest API is deficient, so have raised a public discussions feature request here to track this publicly:

community/community#19570

[kfcampbell]

I still don't think this behavior is available through the API. The only enterprise APIs I can find are here, which isn't what we're after.

I've inquired about this internally and will report back if I hear anything interesting.

[kfcampbell]

I've reached out to the API team and they're aware of the request. At the moment this feature request is not being actively worked on and I can't offer a timeline for it, unfortunately.

[liamoneill]

It appears like some of these settings are present in the GraphQL API (i.e. UpdateEnterpriseAllowPrivateRepositoryForkingSettingInput). Does this provider only use the REST API or would it be possible to use these?

[kfcampbell]

@liamoneill this provider makes use of the GraphQL API as well! If you'd like to create a PR to support this behavior, please feel free!

[silvan02]

I also need the option to enable/disable forking

[github-actions]

👋 Hey Friends, this issue has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Please add the Status: Pinned label if you feel that this issue needs to remain open/active. Thank you for your contributions and help in keeping things tidy!