Hello Pulumi community wave skin tone 2 Since yesterday afte

Question

Hello Pulumi community wave skin tone 2 Since yesterday afternoon pulumi CLI hangs indefinitely whether it be for a `preview` or for `up` The command will initiate and then hang on line 7 with three dots The last change to the stack is minor just an additional statement in a permission policy I can t think it has to do with that Nothing else has changed We re on the latest CLI version since this morning `3 90 1` failed yesterday with version `3 90 0` as well Any idea what could be wrong

little-cartoon-10569 · Answer

Do you get a particular message when you interrupt the update If you get use of closed network connection then it s probably that your temporary credentials have expired

plain-parrot-21984 · Answer

Nope I don t What the snippet shows is all that I get confused

little-cartoon-10569 · Answer

And if you undo the change does it work property

plain-parrot-21984 · Answer

I ve just reverted the last 3 commits and something s actually changing but I don t understand why Let me have a closer look

plain-parrot-21984 · Answer

Apparently this is causing the issue thinking face

little-cartoon-10569 · Answer

What are those s s

little-cartoon-10569 · Answer

Is that printf style interpolation

plain-parrot-21984 · Answer

yep

plain-parrot-21984 · Answer

lines 172 178 are the values

little-cartoon-10569 · Answer

That s not going to work You need to apply to get that Arn That s a future value it s not available at that time

little-cartoon-10569 · Answer

However it shouldn t just hang it should immediately resolve to an error message

little-cartoon-10569 · Answer

Maybe the error message in that particular place is causing troubles with the AWS Role API

little-cartoon-10569 · Answer

It s a pretty big error message

little-cartoon-10569 · Answer

Also is golang really that icky troll

plain-parrot-21984 · Answer

Well the funny thing is I never got any kind of error message

little-cartoon-10569 · Answer

The error message will be in the policy

little-cartoon-10569 · Answer

If you were to print it to console you d see it

little-cartoon-10569 · Answer

The s on line 103 will be an error message not an ARN

plain-parrot-21984 · Answer

Right Well I really didn t expect Pulumi just to hang because of that I didn t really consider the changes being an issue But now that you mention it it makes sense

plain-parrot-21984 · Answer

Thanks for pointing that out I ll find a way to fix it I mean I can construct the ARN instead of fetching it from the creation object itself that should work

little-cartoon-10569 · Answer

You can apply the ARN and build the policy doc as a future value Pulumi handles that fine