Need docs for upgrade path to github_branch_protection_v3

[jspiro]

terraform state mv module.foo.github_branch_protection.this module.foo.github_branch_protection_v3.this does not work, I think this is because the change was introduced after switching maintainers to github. Once you switch providers, you can't read the old state anymore, even though they're actually 100% compatible.

There's only two ways I've found to "upgrade" for folks like me stuck in 2.9:

• Allow it to destroy all the old resources (yeek! not terrible for branch protection, since you will quickly re-add it, but... terrible)
• Manually find and replace in the statefile (double yeek!)

Can someone provide a safe, intended upgrade path?

Op/Ed: _While I appreciate the existence of github_branch_protectionv3, once the graphql API is usable for big orgs, we'll have the same migration nightmare back from v3 to mainline.

Perhaps there could have been a flag to enable the new graphql api, or to enable the old API, or at least an experimental graphql branch protection resource while restoring the old functionality?

I understand there are likely technical reasons why it couldn't be done at this point (incompatible new keywords like pattern, so going backward would be tough for those that upgraded), but the biggest users of this provider are the ones who are ironically suffering the most from a change that should have benefitted them the most. This solution sort of further antagonizes us.

Still, I appreciate it, and I've spent the last five hours figuring out how to make it work.

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

[joebowbeer]

@jspiro what's the status of this?

While I appreciate the existence of github_branch_protection_v3, once the graphql API is usable for big orgs, we'll have the same migration nightmare back from v3 to mainline.

Is the graphql API usable for big orgs now?

[jspiro]

@jspiro what's the status of this?

While I appreciate the existence of github_branch_protection_v3, once the graphql API is usable for big orgs, we'll have the same migration nightmare back from v3 to mainline.

Is the graphql API usable for big orgs now?

No idea. Moved on :-/

[devopsrick]

Nope, still extremely slow.

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

[legoscia]

This is still relevant.