Document using Terrajet together with manually written controllers in the same provider

[muvaf]

What problem are you facing?

Today, we have provider-jet-template that people use to bootstrap their providers that use Terrajet. However, some builders are interested in using Terrajet in their providers that have manually written controllers for each CRD. The most interesting use case is to fill the gaps of the support for resources and later migrate to manually written controllers if needed so that they can provide full coverage for their users.

How could Terrajet help solve your problem?

We have considered this approach for the most popular clouds but opted for having Jet-based providers as separate providers as discussed here. However, most providers are not that big, i.e. having over 400/500/700 CRDs, and they have different constraints regarding how the actual service provider maintains their Terraform codebase and Crossplane codebase. So, it'd be nice to have a document/blog post or just an example provider that shows how you can mix and match. Technically, the Jet providers are very similar and we had that use case in mind from the beginning so I believe it's only a matter of documentation, maybe a few small fixes here and there.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.