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

[Tidschimon]

Expected Behavior

When creating github_actions_environment_variable and github_environment_secret I expect terraform to track the state and create the resources successfully.

note:
since I could not find a better place in the form to put this: I assume this bug is highly related to #2843

Actual Behavior

The resources are created but after applying the plan terraform outputs:

provider "module.old_main.provider["registry.terraform.io/integrations/github"]" produced
│ an unexpected new value: Root object was present, but now absent.

Terraform Version

Terraform v1.14.3
on linux_amd64
...

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

Affected Resource(s)

• github_actions_environment_secret
• github_actions_environment_variable

Terraform Configuration Files

terraform {
  required_providers {
    github = {
      source  = "integrations/github"
      version = "6.9.1"
    }
  }
}

provider "github" {}




resource "github_repository_environment" "environment" {
  repository = "my-repo"
  environment = "default"
}

resource "github_actions_environment_secret" "deployment_key" {
  repository      = "my-repo"
  environment     = github_repository_environment.environment.environment
  secret_name     = "DEPLOYMENT_PRIVATE_KEY"
  plaintext_value = "my-super-secret-key"
}

Steps to Reproduce

run terraform apply to create the resources.

Debug Output

....
  # module.old_main.github_actions_environment_secret.deployment_key will be created
  + resource "github_actions_environment_secret" "deployment_key" {
      + created_at      = (known after apply)
      + environment     = "default"
      + id              = (known after apply)
      + plaintext_value = (sensitive value)
      + repository      = "my-repo"
      + secret_name     = "DEPLOYMENT_PRIVATE_KEY"
      + updated_at      = (known after apply)
    }

...
 

Panic Output

...
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to module.old_main.github_actions_environment_secret.deployment_key, provider "module.old_main.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.
╵

Code of Conduct

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

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[stevehipwell]

@Tidschimon please could you fill out the issue template so someone can look into this for you?

[Tidschimon]

@stevehipwell I edited the description. I also had to boil down the outputs since this is part of a larger project and I can't share specifics, so I hope the code snippet still makes some sense

[stevehipwell]

@Tidschimon it looks like you're using modules? If so do you have the following block in your sub-module?

terraform {
  required_providers {
    github = {
      source  = "integrations/github"
    }
  }
}

[Tidschimon]

@stevehipwell
Yes to both, I do use modules and I do have that block in the sub-module. The snippet shared in the issue description not only specifies "integrations/github" (I remember earlier versions of this provider had a different name), but it also provides the current version "6.9.1". Or do you mean something different, here?

Also, I think I would need this block even if I only had one main module, wouldn't I?

I also think, that this issue is highly related to #2843 but in this case for environment variables and secrets.

[stevehipwell]

@Tidschimon you should have the block with a version in the root module and then the block without a version in sub-modules.

I also think, that this issue is highly related to #2843 but in this case for environment variables and secrets.

I think you may be right.

Are you using github.com or GHEC or GHES?

[Tidschimon]

@stevehipwell
The repository in question is hosted on github.com but behind a coporate organization, so it practically is a private repository. I know, for this I have to specify the organization as the owner of the repository.
So the provider block actually looks something like this

provider "github" {
  owner = "my-organistation"
}

I also can confirm that the variables and secrets are in fact created. It is only terraform and the state that have a hiccup there

[stevehipwell]

@Tidschimon so EMU then? Are you using data residency (non-standard URL)?

[Tidschimon]

@stevehipwell I am not 100% sure of the mechanisms at play. From my perspective we are using organizations .
As far as the relevant part, the repository urls are concerned, these look pretty standard to me.
They follow the scheme: https://github.com/<organisation>/<repository> if that is what you were looking for.
so, coming back to the dummy data I so far referenced, this would be:
https://github.com/my-organisation/my-repo