crossplane / terrajet

Generate Crossplane Providers from any Terraform Provider
https://crossplane.io
Apache License 2.0
290 stars 38 forks source link

Discuss whether we need provider-tf-template repository #41

Closed muvaf closed 3 years ago

muvaf commented 3 years ago

What problem are you facing?

Looking at https://github.com/crossplane-contrib/provider-tf-aws/pull/11 , we have some differences between TF based providers and native ones in terms of how they are packaged or organized structurally.

How could Terrajet help solve your problem?

We can consider provider-tf-template repo but since that'd be another repo to maintain, we first we need to come up with a list of things that are different than native ones so that we can see if it's worth it. A branch in provider-template could be another option.

muvaf commented 3 years ago

Synced with the team offline. For the big 3 (AWS, Azure, GCP) providers, we may not need a provider-tf-template because we might end up merging them into their native variant. However, for the rest (there are 1000+ providers in Terraform Registry), we need to have an easier way of bootstrapping a Terrjet-generated provider. Opened https://github.com/crossplane-contrib/terrajet/issues/60