Closed fhopfensperger closed 2 years ago
Terrajet does not currently support custom providers that use a different HOSTNAME and NAMESPACE than hashicorp.
HOSTNAME
NAMESPACE
hashicorp
If we develop a custom Terraform provider like
# main.tf terraform { required_providers { myprov = { source = "mycompany.io/namespace/myprov" version = "0.1.0" } } }
The current implementation of Terrajet would create the following main.tf.json file in the workspace
main.tf.json
"terraform": { "required_providers": { "namespace": { "source": "mycompany.io/namespace/myprov", "version": "0.1.0" } } }
which fails because the wrong provider name is used.
Terrajet does not currently support custom providers that use a different
HOSTNAME
andNAMESPACE
thanhashicorp
.What happened?
If we develop a custom Terraform provider like
The current implementation of Terrajet would create the following
main.tf.json
file in the workspacewhich fails because the wrong provider name is used.
How can we reproduce it?