stocky-spoon-28903
07/10/2018, 8:10 PMerror: post-step event returned an error: failed to save snapshot: after mutation of snapshot: resource urn:pulumi:pulumi-subnets-test-dev::pulumi-subnets-test::operator-error:aws:Vpc$aws:ec2/vpc:Vpc$aws:ec2/subnet:Subnet$aws:ec2/routeTableAssociation:RouteTableAssociation::demo-public-rta-1 dependency urn:pulumi:pulumi-subnets-test-dev::pulumi-subnets-test::aws:ec2/vpc:Vpc$aws:ec2/routeTable:RouteTable::demo-public-rt refers to missing resource
pulumi destroy
results in the same error message when it fails to load the plugin:
error: failed to load resource plugin aws: failed to perform plugin load callback: failed to save snapshot: after mutation of snapshot: resource urn:pulumi:pulumi-subnets-test-dev::pulumi-subnets-test::operator-error:aws:Vpc$aws:ec2/vpc:Vpc$aws:ec2/subnet:Subnet$aws:ec2/routeTableAssociation:RouteTableAssociation::demo-public-rta-1 dependency urn:pulumi:pulumi-subnets-test-dev::pulumi-subnets-test::aws:ec2/vpc:Vpc$aws:ec2/routeTable:RouteTable::demo-public-rt refers to missing resource
microscopic-florist-22719
07/10/2018, 9:34 PMpulumi stack export
. This will dump the checkpoint to stdout
, so you'll want to redirect to a file.$ pulumi stack export > d.json
urn:pulumi:pulumi-subnets-test-dev::pulumi-subnets-test::aws:ec2/vpc:Vpc$aws:ec2/routeTable:RouteTable::demo-public-rt
. If my guess is correct (and it certainly may not be), you'll find a single reference to this resource in the dependency list for urn:pulumi:pulumi-subnets-test-dev::pulumi-subnets-test::operator-error:aws:Vpc$aws:ec2/vpc:Vpc$aws:ec2/subnet:Subnet$aws:ec2/routeTableAssociation:RouteTableAssociation::demo-public-rta-1
. You'll need to delete that reference from the list.$ pulumi stack import < repaired.json
.bitter-oil-46081
07/10/2018, 11:41 PMaws.iam.Role
that I obtained via aws.iam.Role.get
. Since this resource was "read" it is not in the checkpoint. Presumably https://github.com/pulumi/pulumi/issues/1521 when fixed will address my case.pulumi stack export
, hand editing to remove the bogus URN from the list of dependencies, and then import it and run my program again, after editing it so I didn't immediately fall into this case again.stocky-spoon-28903
07/11/2018, 12:38 AM