root module's terraform.d not searched normally when plugins directory is symlink

[Zordrak]

Terraform Version

0.13.0-rc1

Terraform Configuration Files

terraform {
  required_version = ">= 0.13"
  required_providers {
    shell = {
      source  = "tfregistry.example.org/scottwinkler/shell"
      version = "1.0.0"
    }
  }
}

terraform.d
└── plugins -> ../../../plugins

../../plugins
└── tfregistry.example.org
    └── scottwinkler
        └── shell
            └── 1.0.0
                └── linux_amd64
                    └── terraform-provider-shell_v1.0.0

Description

If you are providing a custom provider plugin binary via the terraform.d directory in a root module, you get different behaviour depending on whether the plugins directory inside terraform.d is a symlink.

If it is not a symlink, the new style directory emulating a registry works as normal.
If it is a symlink, then the new style directory seems to be ignored.

In either case you get write(2, "2020/07/28 18:02:18 [DEBUG] will search for provider plugins in terraform.d/plugins\n", 84) = 84

In either case the old style path of terraform.d/plugins/linux_amd64/terraform-provider-shell is enumerated, going so far as: newfstatat(AT_FDCWD, "terraform.d/plugins/linux_amd64/terraform-provider-shell", {st_mode=S_IFREG|0755, st_size=29781237, ...}, AT_SYMLINK_NOFOLLOW) = 0 but discarding the plugin it finds as unusable (which might be something to do with the plugin or its versionn or the way its built or it might not, I don't know.

Reproducing

• Create a root module that depends on a custom provider plugin as stored in terraform.d using the 0.13 style provider directory path.
• In the root module:
  • terraform init
  • cd terraform.d
  • mv plugins ../../../.
  • ln -snf ../../../plugins
  • cd ..
  • terraform init

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.