[BUG]: cannot set empty status checks in github_branch_protection_v3

[ljw4010]

Expected Behavior

  required_status_checks {
    strict   = true
  }

this configuration can work fine

Actual Behavior

got issues:

│ No subschema in "anyOf" matched.
│ No subschema in "oneOf" matched.
│ Not all subschemas of "allOf" matched.
│ For 'anyOf/1', {"strict"=>true} is not a null. []
│ 
│   with github_branch_protection_v3.create_peotection_rules["master"],

Terraform Version

Terraform: v1.8.0

Affected Resource(s)

github_branch_protection_v3

Terraform Configuration Files

required_status_checks {
    strict   = true
  }

Steps to Reproduce

│ No subschema in "anyOf" matched.
│ No subschema in "oneOf" matched.
│ Not all subschemas of "allOf" matched.
│ For 'anyOf/1', {"strict"=>true} is not a null. []
│ 
│   with github_branch_protection_v3.create_peotection_rules["master"],

Debug Output

No response

Panic Output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[ljw4010]

• unable to update branch_protections for github repos #1147
• Error when creating branch protection google/go-github#2467
  the same issues seems to be appeared again

[cfisher281]

Any idea on a timeline? This has essentially broken the ability to manage branch protection rules for my organization.

[ljw4010]

您的来信已经收到，我会尽快处理，谢谢！！Thank you for your email.

[ljw4010]

Any idea on a timeline? This has essentially broken the ability to manage branch protection rules for my organization.

you can use github_branch_protection to manage branch protection rules, currently I am using it, its working for me

[cfisher281]

We are already using github_branch_protection_v3. That would take a lot of work to move this over.

[ljw4010]

We are already using github_branch_protection_v3. That would take a lot of work to move this over.

We are already using github_branch_protection_v3. That would take a lot of work to move this over.

then you can only wait until this bug is being fixed,hh

[cfisher281]

I understand, that's why I asked if there was a timeline.

[georgekaz]

This is also a dupe of #2093

[kfcampbell]

Thanks @georgekaz, I'll close this and let's track it in #2093 for the future.