Config-Driven Import and the future of Terraformer?

[willvedd]

With config-driven import released in Terraform 1.5.0, there is now an native mechanism that facilitates bulk importing of resources. Cloud providers will still need to provide IDs for resources, but this massively simplifies the problem of exporting Terraform configuration. So much so that I can't help to think that this could massively affect the future of Terraformer.

I think there is still value in a Terraformer-like tool that fetches IDs and creates the import configuration blocks for many providers but it should eliminate a bulk of the complexity with this tool. It's now fairly trivial to home-roll a script or utility that achieves the same thing for the end user.

Granted, there are some considerations like the experimental nature of the feature and the Terraform v1.5.0+ requirement, but these don't seem like non-starters for most devs.

What does everyone else think?