[BUG]: Provider produced inconsistent result after apply (v6.7.3)

[avivamei]

Expected Behavior

Provider should apply successfully

Actual Behavior

Provider fails during apply with error:

Provider produced inconsistent result after apply
When applying changes to , provider "provider["registry.terraform.io/integrations/github"]" produced an unexpected new value: Root object was present, but now absent.

This is a bug in the provider, which should be reported in the provider's own issue tracker.

Terraform Version

Terraform v1.13.4
on linux_amd64

• provider registry.terraform.io/integrations/github v6.7.3

Affected Resource(s)

github_actions_secret

Terraform Configuration Files

terraform {
  required_providers {
    github = {
      source  = "integrations/github"
      version = "~> 6.7"
    }
  }
}

resource "github_actions_secret" "secrets" {
  for_each = var.action_secrets
  repository      = github_repository.repo.name
  secret_name     = each.key
  plaintext_value = each.value
}

Steps to Reproduce

• Use GitHub provider version 6.7.3
• Define a github_actions_secret resource in your configuration
• Run terraform init
• Run terraform plan

Debug Output

Panic Output

Code of Conduct

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

[dominictarro]

Same issue starting today.

[JamesGoodhouse-at]

Likely duplicate of #2838 and #2839

[avivamei]

Likely duplicate of #2838 and #2839

The errors in those issues seem to be resolved with v6.7.3, but I am getting different errors with v6.7.3

[rohitpaulk]

Running into the same here with a github actions secret resource.

[pnancarrow]

does this have anyone else completely stuck? I can't downgrade or I end up with:

 Error: Resource instance managed by newer provider version

[dominictarro]

does this have anyone else completely stuck? I can't downgrade or I end up with:

I downgraded to =6.7.0 and had to reimport a bunch of resources.

[nickfloyd]

So sorry for the trouble here. I think I've tracked down the issue to the Update implementation.

Turns out when a Terraform resource has an Update function defined (which was recently added), the Terraform SDK requires that any field that can change must either have ForceNew: true (meaning changes require resource recreation) or for that field to be a computed-only field.

The destroy_on_drift field is a provider config setting that controls how drift detection works - it's not a field that maps to the GitHub API. When implementations try to change this field Terraform will execute the plan properly ✅ but fail on the apply because the Update function didn't know how to handle the destroy_on_drift change.

You should be able to work around this issue while I work up a patch by pinning to v6.7.1 though that even looks problematic for some.

Working on a patch right away. Again apologies for the trouble.