I am trying to use statuscake to setup monitoring of a website. It works fine when I do this in a standalone file. However when I try to break it out into a module, it fails with an error message when I run terraform init. The error message is Initializing modules... - statuscake in ..\..\modules\s…

It’s best practice to have a required_providers block in every module which specifies which providers the module uses. This becomes necessary rather than recommended when the module uses providers from non-HashiCorp namespaces. Adding the required_providers block to your module should fix this issue…

alisdair that worked perfectly. Thanks

I have the same problem, but I don’t understand the answer. How am I doing this wrong in this example? terraform { required_providers { bless = { source = "registry.terraform.io/chanzuckerberg/bless" version = "~> 0.5" } } required_version = ">= 0.13" } data "aws_region"…

The terraform/required_providers block is scoped to the individual module. That means you need to repeat it (but not the provider block) inside each module. Since cztack/bless-ca at main · chanzuckerberg/cztack · GitHub doesn’t do this, it means that module has not been updated to be compatible wi…

I’ve been bitten by this as well, and since no one has explicitly said this, then: When a child module uses a provider outside of the Hashicorp namespace, then you are required to duplicate the the entire terraform { required_providers { } } code block in every module where that provider is used, r…

[image] blue928: In my opinion, this inconsistent behavior should be considered a bug / design flaw. It’s a compatibility measure to ease upgrading from earlier Terraform versions. I’m inclined to agree with you that it’s inelegant that the defaulting behaviour was retained into the 1.x seri…

I agree but honestly there was a limited appetite for more breaking changes in the last few releases before 1.0 and so we had to focus on only a few things that would have a significant impact on our ability to keep improving Terraform under the compatibility promises, and this one (along with many …

I can live with inconsistency, however when there is, the documentation needs to highlight this inconsistency in big red flashing lights. Hours wasted :frowning:

Hi @david7 , Can you share which parts of the documentation you were referring to when you had this problem? This behavior is mentioned in a few places in the documentation, but of course the problem with implicit behavior is that it’s not something you explicitly chose to rely on and therefore you…

I was following the tutorial albeit using a different provider. Build and Use a Local Module | Terraform | HashiCorp Developer . This is the misleading paragraph : Notice that there is no provider block in this configuration. When Terraform processes a module block, it will inherit the provider fro…

Using a non hashicorp provider in a module

Terraform

Topic		Replies	Views
Terraform trying to install incorrect provider Terraform	9	15345	February 24, 2023
Use non Hashicorp provider in module with for_each Terraform	6	5619	February 8, 2022
Module tries to instantiate wrong provider: failed to instantiate provider "xxx" to obtain schema: unavailable provider Terraform	7	2572	December 9, 2022
Terraform provider required Terraform	0	271	January 21, 2021
Hetzner cloud provider incorrectly inherited in modules Terraform Providers	1	1136	January 24, 2023

Using a non hashicorp provider in a module

Related topics