1. I had scenarios where one of my terraform deplo...
# general
6. I had scenarios where one of my terraform deployments had to be split into 2 or more deployments. Or I needed to move some resources from top-level resources into a module. I could use
terraform state mv|rm
terraform import
to achieve this. Is it supported in pulumi?
Also actively in progress. Import support in https://github.com/pulumi/pulumi/issues/1662 and https://github.com/pulumi/pulumi/issues/1635. And `alias`s to allow changing the name of a resources in https://github.com/pulumi/pulumi/issues/458. It's possible to manually edit state files to achieve both goals already today, but will be easier once these features land.
Noted - thanks
One more question on this: would the issues listed above support moving top-level resources from a pulumi program into a https://pulumi.io/reference/pkg/nodejs/@pulumi/pulumi/#ComponentResource (e.g. in a reusable npm package)?
Yes - that's one of the key topics raised in and tracked by https://github.com/pulumi/pulumi/issues/458. We believe the "aliases" approach there can be made to support this - but we still have work to do to finish the design of this.
👍 1