We are seeing pulumi take 3+ minutes to read awsec2Vpc and subnets during an update? This is slowing our deployments quite a bit, any reason this might be happening?

const vpc = awsx.ec2.Vpc.fromExistingIds("vpc", {
  privateSubnetIds: vpcPrivateSubnetIds,
  publicSubnetIds: vpcPublicSubnetIds,
  vpcId
});

did this recently start happening?

Could you do either/both of: 1. Capture and share a trace per https://github.com/pulumi/pulumi/issues/3257#issuecomment-534629119. 2. Run

TF_LOG=trace pulumi up --logtostderr -v=9 2> out.txt

and see if that gives any indication of what is taking time.

Yes, will do

btw @white-balloon-205, this is what I got running the command in the linked issue

[snip]
Diagnostics:
  pulumi:pulumi:Stack (service-prod):
    flag provided but not defined: -tracing
    Usage of tf-provider-flags:
      -get-provider-info
                dump provider info as JSON to stdout
 
    flag provided but not defined: -tracing
    Usage of tf-provider-flags:
      -get-provider-info
                dump provider info as JSON to stdout
 
    flag provided but not defined: -tracing
    Usage of tf-provider-flags:
      -get-provider-info
                dump provider info as JSON to stdout
 
    flag provided but not defined: -tracing
    Usage of tf-provider-flags:
      -get-provider-info
                dump provider info as JSON to stdout

The flag is

--tracing

- but you also may need to be on the latest

1.2.0

release to have that available.