Bring your Terraform to Crossplane

In this webinar, we'll try to cover to use cases when Terraform and Crossplane might work together.

1. You're a heavy Terraform user, but you want to move to Crossplane. Let's say you already have an opinionated "RDS instance" Terraform module. You can now write a Crossplane Composition that uses that Terraform module to get your migration started with low effort and risk, then transparently migrate folks over to a 'native' Crossplane Composition that satisfies the same XR when you're ready.

Additional info:

[silviomsilva]

Great content! Thank you both for that! I followed the steps from the video and make the same example works but I note that the Terraform Version used by Crossplane Experimental Terraform Provider is 1.0.1 (checking the contents of Terraform State) even when I set the "required_version = ">= 1.0.5, < 2.0.0" block on Terraform Code.

I have an use case that we'll need to support multiple Terraform versions for some time and, because of that, we're packaging the Terraform Code + Terraform Binary + Modules into a Container Image and running it using Pipelines while we work on the update in smaller pieces.

I'd like to know if is there a way to accomplish that using Crossplane?

I see that a Workspace Kind is used to reference a Terraform Module or Inline Terraform Code but, if it could be possible to tell to Crossplane to only execute our customized Container Images with some Environment Variables and get the Terraform Outputs from there (it could be as text plain or json format).

Maybe we need to create a Provider for that? I'll be grateful if you could give any thoughts about it.