This message was deleted.
# general
s
This message was deleted.
g
Happy to take this to the #CRH5ENVDX channel if that's a better place for it.
b
Sounds like the issue is the "hard limit" of the 1 hour situation. I'd work to get that fixed first, but past that, theres no way for pulumi to check your session and send a request to some outside system asking for a refresh? Wont happen.. so, what you should try is see what happens if you manually update the role variables during execution of pulumi. My guess is that you'll want to use some type of side process that is checking the creds and refreshing them as needed. Or maybe, you use a script to get temp creds, write them to a file, and update that file. Something like that. Pulumi uses the terraform providers, and those make a bunch of individual calls so your question about a single asynchronous call is not likely to happen, unfortunately.
Of course it's possible for them to change their program to handle something like this, but seems like it's out of scope. Maybe check for a program that will refresh creds automatically? Maybe one is out there.
g
Thanks -I'll have a poke around.
l
@great-vr-65723 2.5 year open issue on the TF front: https://github.com/terraform-providers/terraform-provider-aws/issues/1351 Since the pulumi provider is based on the TF one, this issue is applicable here too.