https://pulumi.com logo
Title
s

shy-butcher-69105

10/14/2021, 10:21 AM
Hi everyone. Loving pulumi 🙂 On a
pulumi up
today I'm getting a non-ending run (at least 17m). • logging with
v=9
didn't reveal anything • tracing with
pulumi up --logtostderr -v=9 --tracing=file:./trace
then
PULUMI_DEBUG_COMMANDS=1 pulumi view-trace ./up.trace
shows: ◦ 17m in
pulumi plan
, which includes 17m in both
/pulumirpc.LanguageRuntime/Run
and
/pulumirpc.ResourceProvider/Configure
is there a way to debug this further? (for context, Win10 powershell (replicates with CMD), pulumi v3.14.0, making a single change on AWS.IAM, using hosted
w

witty-candle-66007

10/14/2021, 2:41 PM
Often when I see a hanging pulumi up it’s because one is using AWS credentials that have expired. Could this be the case here?
❤️ 1
s

shy-butcher-69105

10/14/2021, 2:57 PM
it could well be. I'll check
l

little-summer-88406

10/14/2021, 2:58 PM
var current = Output.Create(Aws.GetCallerIdentity.InvokeAsync());
var accountId = current.Apply(current => current.AccountId);
and then add that to output of your stack. So your stack does nothing (no change) only read..
translate to python or go.. ^
comment out any ops such as your IAM change
s

shy-butcher-69105

10/14/2021, 3:02 PM
Thanks all. It was expired credentials.