No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I think to do this effectively, you’d need to ensure the mapping between names is the same for both types of code. You can reconstitute terraform state with import and ID only refresh as a last resort 

Thanks! Yes, the solution will involve `terraform import`. It probably doesn't exists ... but a script that can read a pulumi export state file and execute the appropriate `terraform import` for all the resources to generate the terraform files. This in theory should work I believe :slightly_smiling_face:

It would work - but will need the name mapping to be useful 

thanks <@UB8A66MPS>! Just providing an update here ... my team really likes Pulumi but we're not ready to completely drop Terraform ... as with anything, it takes some to evaluate, experiment, and adopt ... and then transition from the old to the new. So a tool that can translate Pulumi stacks to Terraform files will be very useful :slightly_smiling_face:

For example, a workflow I'm trying out is as follows: 1) Develop and test with Pulumi for new projects, and 2) Then, create the _equivalent_ Terraform files when we're ready to deploy into production. The Terraform files are stored in our master github repo for all our infrastructure.