This message was deleted.

you will unfortunately, yes. Do you know where this route table came from? generally you'll need to set up your own route table in the Pulumi state to avoid this

Got it, thanks. Pretty sure this route table in fact is defined in Pulumi, which I've assigned to the VPC using a

MainRouteTableAssociation

. Not sure what's gone wrong here...

any chance you can share some code?

Yeah, nothing too fancy in this part 🤷

var vpcRouteTable = new RouteTable($"{stack}-vpc-route-table-public", new RouteTableArgs
            {
                VpcId = vpc.Id,
                Routes = new []
                {
                    new RouteTableRouteArgs
                    {
                        CidrBlock = "0.0.0.0/0",
                        GatewayId = igw.Id,
                    }
                }
            });

            var vpcRouteTableAssociation = new MainRouteTableAssociation($"{stack}-vpc-route-table-association",
                new MainRouteTableAssociationArgs
                {
                    VpcId = vpc.Id,
                    RouteTableId = vpcRouteTable.Id
                });

When I create VPCs, I generally never use the main route table association because it creates some weird dependency/ordering issues which it seems like you're seeing

Thanks again, I will steer away from it going forward 😄