Hey, Is there an open issue about Pulumi stuck on ...
# aws
m
Hey, Is there an open issue about Pulumi stuck on running… / destroying… / refreshing… when using token to authenticate with AWS? I’m using onelogin-aws-cli-assume-role too to authenticate and there is no error when token has expired it just keeps retrying endlessly…
c
From my experience using an expired token fails quite fast
s
That is a cool tool. I might start using it. As for your question, I noticed the following in the documentation
Copy code
The credentials only last for 1 hour so you can also make it regenerate and update the credentials file by using the --loop option.
m
Regarding the expire it’s 24 hours in our policy but I sometimes forget to re-authenticate.. And it does not provide an error.