Setting members_can_fork_private_repositories resets organisational fork policy

[fatbasstard]

We're now using the github_organization_settings to configure some organisational settings (instead of "manual") and we noticed that settings members_can_fork_private_repositories works in unexpected ways with the organisational settings:

We had forking set to User accounts, imported the github_organization_settings resource (where members_can_fork_private_repositories apparantly is set to True and not TF changes this to the "Default" Organisations within this enterprise.

This is quite unexpected behaviour, and after reading up other issues decided to remove this setting from the resource entirely. When removing it TF actually said it would change the setting (update members_can_fork_private_repositories : true change to false). But the setting is now kept intact.

So:

• Organisation settings and Forking looks "off" (could be related to Enterprise)
• Is there a resource to change the forking policy of an (enterprise) organisation?

Related links:

• https://github.com/integrations/terraform-provider-github/issues/1199
• https://github.com/integrations/terraform-provider-github/issues/1333
• https://github.com/integrations/terraform-provider-github/pull/1362

[kfcampbell]

I'm sorry, I'm not quite sure what you mean by:

This is quite unexpected behaviour, and after reading up other issues decided to remove this setting from the resource entirely. When removing it TF actually said it would change the setting (update members_can_fork_private_repositories : true change to false). But the setting is now kept intact.

Would you mind rephrasing this for me a little differently and I can try to help troubleshoot?

[fatbasstard]

Hi @kfcampbell,

Organisation setting in the GUI:

Applying Terraform with the following (which gives no changes):

resource "github_organization_settings" "connectedbrewery" {
...
  members_can_fork_private_repositories = true
...
}

[github-actions[bot]]

👋 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!

[fatbasstard]

Any update on this issue?

[tpham-drw]

We use github_organization_settings with members_can_fork_private_repositories ~but are not seeing the sub-setting for the fork destination being reset by Terraform~ I spoke too soon - if the TF apply touches github_organization_settings, even though the change is not shown in the plan, it will reset the settings.

It would be good to be able to set this in TF instead of manually though.