dbtcloud_repository resource produces inconsistent result with git_clone_strategy during apply

[VuKrampHub]

Describe the bug

The dbtcloud_repository resource produces an inconsistent result during terraform apply. The git_clone_strategy attribute is configured as "github_app" but the provider returns "deploy_key" after creation, causing Terraform to report a provider bug.

Error message

Error: Provider produced inconsistent result after apply  

When applying changes to  
module.service.module.dbt_cloud_project[0].dbtcloud_repository.default,  
provider "provider[\"registry.terraform.io/dbt-labs/dbtcloud\"]" produced an  
unexpected new value: .git_clone_strategy: was cty.StringVal("github_app"),  
but now cty.StringVal("deploy_key").  

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

Resource configuration

resource "dbtcloud_repository" "default" {
  project_id             = dbtcloud_project.default.id
  remote_url             = <valid_github_url>
  github_installation_id = <valid_github_installation_id>
  git_clone_strategy     = "github_app"
}

Expected behavior

The git_clone_strategy should remain as "github_app" after the resource is created, matching the configured value. The provider should not change this value during the apply operation.

Config (please complete the following information):

• dbt Cloud provider version [1.1.1] and [1.1.4]

Additional context

• This issue occurs during terraform apply in a CI/CD pipeline recently. Previous run about 15 - 30 days ago was without such issue.
• The resource is being created as part of a module structure
• The repository URL uses the git:// protocol
• The issue appears to be related to the provider's handling of the git_clone_strategy attribute, where it may be defaulting to or forcing "deploy_key" regardless of the configured value

[trangkramp]

We also tried to revert terraform dbt cloud provider from v1.0 to v0.3, and the error persists.

For example, dbt-macros is provisioned today, although in terraform config, git_clone_strategy = "github_app" and the build ran successfully, in dbt Cloud UI, Clone strategy gets changed to deploy_key. Environments and jobs are configured correctly, but the GitHub repo cannot be cloned in either Studio IDE or triggered jobs. We have double checked that the repo is included in the access list of dbt Cloud EMEA app.

Here is the error we got when trying to clone the repo:

git clone git://github.com/kramphub/dbt-macros.git /usr/src/develop/user-4927/environment-30070/repository-12488
Cloning into '/usr/src/develop/user-4927/environment-30070/repository-12488'...
fatal: unable to connect to github.com:
github.com[0: 140.82.121.3]: errno=Connection timed out

Versus dbt-hr-nl with no change history over the last 90 days: