argocd Provider 7.9.0, 7.10.0 - githubapp_id, githubapp_installation_id are both set to null

[Trikenstein]

Terraform Version, ArgoCD Provider Version and ArgoCD Version

Terraform version: v1.12.2
ArgoCD provider version: 7.9.0 and 7.10.0
ArgoCD version: v2.12.2+560953c

Affected Resource(s)

• argocd_repository

Terraform Configuration Files

#-----------------------------------------------------------
# these resources are located in a module named "MyModule"
#-----------------------------------------------------------

resource "argocd_repository" "source-repo" {
  repo = "https://github.com/MyCompany/MyRepo.git"

  githubapp_id              = 12345
  githubapp_installation_id = 987654
  githubapp_private_key     = var.githubapp_private_key
}

resource "argocd_application" "application" {
  # skip
  # this resource is not affected by the problem described in this issue

  depends_on = [
    argocd_repository.source-repo
  ]
}

Steps to Reproduce

1. terraform apply -target module.MyModule

The terraform plan detects a change for the attributes githubapp_id and githubapp_installation_id while there is NO CHANGE at all for those values.

  # module.MyModule.argocd_repository.source-repo will be updated in-place
  ~ resource "argocd_repository" "source-repo" {
      ~ connection_state_status   = "Successful" -> (known after apply)
      + githubapp_id              = (sensitive value)
      + githubapp_installation_id = (sensitive value)
      ~ id                        = "https://github.com/MyCompany/MyRepo.git" -> (known after apply)
      ~ inherited_creds           = false -> (known after apply)
        # (6 unchanged attributes hidden)
    }

Expected Behavior

As our githubapp_id and githubapp_installation_id values are unchanged. There should be no change detected related to argocd_repository. Confirmed by reverting the argoproj-labs/argocd provider to version 7.8.2. The Terraform plan didn't show any change related to argocd_repository

Actual Behavior

With argoproj-labs/argocd provider version 7.9.0 and 7.10.0, at the time of this writing, ie. 2025-07-31, Terraform detects change in argocd_repository on the two attributes githubapp_id and githubapp_installation_id. We thought that is an harmless change and went ahead to apply the terraform plan.

After that, githubapp_id and githubapp_installation_id are both set to null . Verified by terraform state pull ./MyTFstate.json. Reviewing the MyTFstate.json file, search for keyword "githubapp_id": and we see

    {
      "module": "module.MyModule",
      "mode": "managed",
      "type": "argocd_repository",
      "name": "source-repo",
      "provider": "provider[\"registry.terraform.io/argoproj-labs/argocd\"]",
      "instances": [
        {
          "schema_version": 0,
          "attributes": {
            "connection_state_status": null,
            "enable_lfs": false,
            "enable_oci": false,
            "githubapp_enterprise_base_url": null,
            "githubapp_id": null, # <----- BUG -----
            "githubapp_installation_id": null, # <----- BUG -----
            "githubapp_private_key": "-----BEGIN RSA PRIVATE KEY- blabla"

Subsequently, any terraform apply related to any ArgoCD resource (eg. create new argocd_application) failed immediately with the error

│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to module.MyModule.argocd_repository.source-repo,
│ provider "provider[\"registry.terraform.io/argoproj-labs/argocd\"]" produced an unexpected new value: .githubapp_id: inconsistent values for
│ sensitive attribute.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to module.MyModule.argocd_repository.source-repo,
│ provider "provider[\"registry.terraform.io/argoproj-labs/argocd\"]" produced an unexpected new value: .githubapp_installation_id: inconsistent
│ values for sensitive attribute.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

WORK AROUND

Revert argoproj-labs/argocd provider to version 7.8.2

[the-technat]

@Trikenstein thanks for raising this issue! That sounds like something with the migrated resources isn't right. Will try to look at it next week.

[Trikenstein]

@the-technat Thanks for willing to address the issue. I suppose you meant "the migrated resources" is something internal to the argocd provider. Because on our side we didn't migrate anything. Just wanted to create a new argocd_application.

Looks like the provider is undergoing some breaking changes. You guys might want to bump the provider major version to 8.x

[the-technat]

Yeah with migrated resources I meant the transition from the Terraform SDKv2 to the Plugin Framework. Theoretically this isn't a breaking change as it should simply work with existing resources, but we haven't tested all fields.

But thanks for the input. If this transition to the Plugin Framework keeps introducing new bugs we might be better of bundling it in a breaking change...

[blakepettersson]

@Trikenstein can you try version 7.10.1 to verify that the issue has been fixed?

[ingoldooo]

Hey guys, the update brings an issue

We got repositories created with terraform through argocd provider. After the recent provider's upgrade - the following fields are marked as to be updated:

      ~ connection_state_status       = "Successful" -> (known after apply)
      ~ id                            = "$ssh_repo_url" -> (known after apply)
      ~ inherited_creds               = false -> (known after apply)

Though, after applying it for ~80 minutes I just interrupted the process.

Versions below 7.10.1 are not showing any updates in repo.