Skip to content

[BUG]: v6.7.4 causes Internal validation error during TF InitΒ #2855

@AndrewUnderwoodAtFanatics

Description

Expected Behavior

I would expect TF that was working prior to the v6.7.0 release would resume working after the v6.7.4 fix.

v6.7.0, v6.7.1, v6.7.2, and v6.7.3 gave us errors at the end of the apply but unfortunately v6.7.4 is giving us errors at the beginning of the plan.

Actual Behavior

Error: InternalValidate

  with provider["registry.terraform.io/integrations/github"].xxx

Internal validation of the provider failed! This is always a bug
with the provider itself, and not a user issue. Please report
this bug:

resource github_actions_organization_secret: All fields are ForceNew or
Computed w/out Optional, Update is superfluous
resource github_actions_secret: All fields are ForceNew or Computed w/out
Optional, Update is superfluous

Error: InternalValidate

  with provider["registry.terraform.io/integrations/github"].xxx,
  on main.tf line 44, in provider "github":
  44: provider "github" {

Internal validation of the provider failed! This is always a bug
with the provider itself, and not a user issue. Please report
this bug:

resource github_actions_organization_secret: All fields are ForceNew or
Computed w/out Optional, Update is superfluous
resource github_actions_secret: All fields are ForceNew or Computed w/out
Optional, Update is superfluous

Module versions in this stack

  - Using olivr/gpg v0.2.1 from the shared cache directory
  - Using mastercard/restapi v2.0.1 from the shared cache directory
  - Using tchupp/env v0.0.2 from the shared cache directory
  - Using hashicorp/aws v5.6.2 from the shared cache directory
  - Using integrations/github v6.7.4 from the shared cache directory <---- integrations/github v6.7.4
  - Using hashicorp/tls v4.1.0 from the shared cache directory
  - Using datadog/datadog v3.78.0 from the shared cache directory

Terraform Version

Terraform v1.13.4
on linux_amd64

Affected Resource(s)

  • github_actions_organization_secret

Terraform Configuration Files

I'm sorry, I can't share this publicly but I can share privately if there's a way to accomplish this.

Steps to Reproduce

No response

Debug Output

Panic Output

Code of Conduct

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Status: TriageThis is being looked at and prioritizedType: BugSomething isn't working as documented

    Type

    No type

    Projects

    Status

    In Review

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions