icy-london-5840302/13/2020, 5:22 PM
and then pulumi sees the need to destroy and recreate. I have create before destroy set. Then it tries to create
. Let's say I'm good with that but I need the data moved with the change. I could make an ssm automation document that could take a source bucket as input and a destination bucket as input and copy everything over. Would I be able to trigger the execution of that ssm automation document or any other type of script to handle that phase of the pulumi resource replacement lifecycle? I am not currently working on solving this but I'm just curious.