glamorous-printer-14057
05/28/2020, 2:46 AMpulumi up
is now stuck hanging for me, and I’m not quite sure what changed. is there some way to get out of this state?pulumi up --logtostderr -v=9
gives
I0527 19:44:28.526972 46303 eventsink.go:59] Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id
I0527 19:44:28.526989 46303 eventsink.go:62] eventSink::Debug(<{%reset%}>Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id<{%reset%}>)
I0527 19:44:28.527333 46303 eventsink.go:59] AWS Auth provider used: "EnvProvider"
I0527 19:44:28.527344 46303 eventsink.go:62] eventSink::Debug(<{%reset%}>AWS Auth provider used: "EnvProvider"<{%reset%}>)
I0527 19:44:28.527823 46303 eventsink.go:59] Trying to get account information via sts:GetCallerIdentity
I0527 19:44:28.527832 46303 eventsink.go:62] eventSink::Debug(<{%reset%}>Trying to get account information via sts:GetCallerIdentity<{%reset%}>)
I0527 19:44:28.538582 46303 eventsink.go:59] Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id
I0527 19:44:28.538599 46303 eventsink.go:62] eventSink::Debug(<{%reset%}>Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id<{%reset%}>)
I0527 19:44:28.538994 46303 eventsink.go:59] AWS Auth provider used: "EnvProvider"
I0527 19:44:28.539003 46303 eventsink.go:62] eventSink::Debug(<{%reset%}>AWS Auth provider used: "EnvProvider"<{%reset%}>)
I0527 19:44:28.539355 46303 eventsink.go:59] Trying to get account information via sts:GetCallerIdentity
pulumi:pulumi:Stack elementl-dev running..
I0527 19:44:29.016275 46303 eventsink.go:59] Trying to get account information via sts:GetCallerIdentity
I0527 19:44:29.016311 46303 eventsink.go:62] eventSink::Debug(<{%reset%}>Trying to get account information via sts:GetCallerIdentity<{%reset%}>)
I0527 19:44:29.080942 46303 eventsink.go:59] Trying to get account information via sts:GetCallerIdentity
pulumi:pulumi:Stack elementl-dev running
gentle-diamond-70147
05/28/2020, 4:48 PMpulumi config set aws:skipRequestingAccountId true
or pulumi config set aws:skipCredentialsValidation true
(from https://www.pulumi.com/docs/intro/cloud-providers/aws/#configuration) to see if you get different behavior. That's not necessarily a fix, but might help troubleshoot it.glamorous-printer-14057
05/28/2020, 5:05 PMpulumi up
issue for now