James Bardin

@nfagerlund, IIRC that limitation was intentional, because the namespace was required to be a valid GitHub organization name, which also disallows underscore (At least one reason is because the organization...

Yeah, that is a different codepath which is even more restrictive for similar reasons. The “system” segment must also be a valid provider local name.

Hi @2rs2ts, Thanks for opening the issue. A workspace is something that exists _within_ a backend, so having a separate backend per workspace doesn't really fit the current model. However,...

Hi @2rs2ts, I appreciate the feedback. Workspaces only exist within a backend, or to state it another way, until a backend is loaded (including the default "local" backend) there are...

@2rs2ts, Sorry, we don't have a set timeline for that enhancement. Most users and organization use a single backend per config, so there's usually nothing to work around. If the...

Hi @roy-work, Sorry you're having trouble with this, does the output of the suggested command of `terraform providers` point to the module which is associating the `cloudflare` name with `hashicorp/cloudflare`?...

@toMyLord, you likely have a module missing the necessary `required_providers` entry. Try the instructions above, and if you have questions you can ask in [the community forum](https://discuss.hashicorp.com/c/terraform-core) where there are...

@blue928, If a provider is not in the default hashicorp namespace, terraform needs to know exactly which provider is used within the module., so that is working as designed. To...

Terraform will be able to detect if there is a DNS _failure_, but more often than not misconfigured DNS results in no response at all. Without running some extra diagnostics...

Hi @alexwlchan, Thanks for filing the detailed issue. I'm going to reclassify this as an enhancement, since everything you've shown here is the designed behavior of Terraform. If you store...