Hello!
- Vote on this issue by adding a 馃憤 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
Consider supporting adding translated resources to a pre-existing Pulumi Stack State with some existing resources. This will make the tool more flexible.
Ideally this operation should be idempotent that is repeatedly adding the same translated TF resources should not cause them to be added twice as that can lead to confusion.
Currently the main workflow for this tool implies creating a mostly fresh Pulumi Stack state that represents N translated Terraform resources. The starting point is a Stack State with only 1 synthetic resource (State) and that is essentially an empty project. If there are pre-existing resources the tool gives up with an error.
Affected area/feature
Hello!
Issue details
Consider supporting adding translated resources to a pre-existing Pulumi Stack State with some existing resources. This will make the tool more flexible.
Ideally this operation should be idempotent that is repeatedly adding the same translated TF resources should not cause them to be added twice as that can lead to confusion.
Currently the main workflow for this tool implies creating a mostly fresh Pulumi Stack state that represents N translated Terraform resources. The starting point is a Stack State with only 1 synthetic resource (State) and that is essentially an empty project. If there are pre-existing resources the tool gives up with an error.
Affected area/feature