https://pulumi.com logo
Title
b

big-piano-35669

07/14/2018, 4:17 PM
@orange-airplane-70350 @able-tomato-34262 Great discussion on importing existing resources. Importing existing resource state is indeed a "work in progress" for us. We have a variety of GitHub issues tracking conversion tools more broadly, but I just created one to track the idea of a
pulumi import
command: https://github.com/pulumi/pulumi/issues/1635. If you want to do it by hand today, you can, but it's very much a manual process along the lines of what @able-tomato-34262 suggests (
pulumi stack export
your checkpoint state, add the empty resources to it,
pulumi stack import
it, and then run
pulumi refresh
to read in all the state). I realize this is cumbersome and if you'd like help, we're happy to spend some time with you.
pulumi import
would automate this process.
s

stocky-spoon-28903

07/14/2018, 4:35 PM
Does the Terraform bridge have import support?
There are specific nasty cases (for AWS in particular, but also for other things) where to do a meaningful import you have to map from the user-facing ID for more things (e.g. if you want route table rules in addition to the route table) - the TF provider protocol has support for this built in which applies to most resources already.
b

big-piano-35669

07/14/2018, 4:42 PM
It does not yet, but I agree with you completely that this is the way to go. cc @microscopic-florist-22719 as I know he has done some thinking here.
s

stocky-spoon-28903

07/14/2018, 4:43 PM
👍 Feel free to throw any concerns/questions about that this way, I either implemented or reviewed the majority of the import logic for Terraform originally.
b

big-piano-35669

07/14/2018, 5:17 PM
Sweet, thank you so much!