Closed muvaf closed 2 years ago
Since we'll be doing two Terrajet-generated provider releases, we'll be able to go through all details of this. So I'll tackle this issue today even though it's marked as beta
, not to go back and load all that context again later.
Just so I don't forget, we should put generation build constraints to cmd/generator
so that we don't need to compile all TF provider when we get a build of the provider.
Created the repo: https://github.com/crossplane-contrib/provider-tf-template
Requires more polishment but I could generate and successfully tested provider-tf-kafka from https://registry.terraform.io/providers/Mongey/kafka/latest/docs
Closing since https://github.com/crossplane-contrib/provider-tf-template is ready for use.
What problem are you facing?
Terrajet providers have different
Dockerfile
and several other things that we need to do lots of manual plumbing to make provider-template work.How could Terrajet help solve your problem?
We can have a
provider-tf-template
people could just use to bootstrap a Terrajet-based provider.