able-tomato-34262
07/03/2018, 2:13 PMpulumi config set aws:region eu-west-1
( my resources were previously in us-east-1 ) and I expected pulumi to destroy all my resources in us-east-1
to create them in eu-west-1
but pulumi seemed to lost track of my resources then, I couldn't do anything, even destroy. Is that the expected behaviour ?big-soccer-75859
07/03/2018, 2:17 PMable-tomato-34262
07/03/2018, 2:25 PMbig-soccer-75859
07/03/2018, 2:27 PMable-tomato-34262
07/03/2018, 2:28 PMwhite-balloon-205
07/03/2018, 3:21 PMpulumi
always uses a single set of configuration for any given cloud provider during an update - so one you change your aws:region
to eu-west-1
, all calls to AWS from Pulumi will go to Ireland not Virginia. However, the delete operations on the old resources should instead use the provider configuration that was used to create them. This is something we plan to address.
Fortunately, this should be fairly rare, and as you noticed later, you can work around by switching region back, destroying, then moving region forward (or standing up a new stack for the new region and destroying the old stack).big-soccer-75859
07/03/2018, 3:24 PMable-tomato-34262
07/03/2018, 3:25 PMbig-soccer-75859
07/03/2018, 3:26 PMable-tomato-34262
07/03/2018, 3:26 PMbig-soccer-75859
07/03/2018, 3:27 PMable-tomato-34262
07/03/2018, 3:28 PMbig-soccer-75859
07/03/2018, 3:31 PMable-tomato-34262
07/03/2018, 3:32 PMbig-soccer-75859
07/03/2018, 3:32 PMable-tomato-34262
07/03/2018, 3:32 PMbig-soccer-75859
07/03/2018, 3:32 PMable-tomato-34262
07/03/2018, 3:33 PMbig-soccer-75859
07/03/2018, 3:37 PMbig-piano-35669
07/03/2018, 3:49 PMpulumi stack export
command (and import it using pulumi stack import
).