When using the github_repository_ruleset and enabling the required_status_checks with a required_check config block, the integration_id is an optional value. When a required_check is configured with only the context value provided, the integration_id should be ignored.
When using the github_repository_ruleset and enabling the required_status_checks, if the integration_id is not supplied, once the value is updated on the github side (if you have something like Github Advanced Security), the terraform plan results show that the integration_id has been updated. Limitation in Lifecycle ignore_changes means that this value can't be ignored without ignoring all required_check blocks that have been configured.
I have a problem which seems to be connected with yours. I can't apply a plan with integration_id other than 0, because of the same error (422 error code). Were you able to use non-0 integration_id @strachg?
Expected Behavior
When using the
github_repository_ruleset
and enabling therequired_status_checks
with arequired_check
config block, the integration_id is an optional value. When arequired_check
is configured with only thecontext
value provided, the integration_id should be ignored.Actual Behavior
When using the
github_repository_ruleset
and enabling therequired_status_checks
, if the integration_id is not supplied, once the value is updated on the github side (if you have something like Github Advanced Security), the terraform plan results show that the integration_id has been updated. Limitation in Lifecycle ignore_changes means that this value can't be ignored without ignoring allrequired_check
blocks that have been configured.If the value returned on subsequent
terraform plan
executions is used initially, when creating the required_check, the following error is returned.Terraform Version
Terraform v1.9.2 on darwin_arm64
Affected Resource(s)
Terraform Configuration Files
Steps to Reproduce
No response
Debug Output
No response
Panic Output
No response
Code of Conduct