This message was deleted.
s
This message was deleted.
b
Please add a step before the actions run to list the stacks. Is the access token you’re using associated with the org in question?
l
Also, there should be no project in the stack name.
--stack kettleos/dev
s
why did it work before and it stopped?
l
Check the workflow code.. did it change?
s
thanks @billowy-army-68599 and @little-cartoon-10569 trying to respond as best I can and get info as quick as I can
b
Could be a few reasons, but my guess is that more than likely the user associated with access token no longer has access to the org?
💡 1
s
prior to creating the issue, we were only pinned to
action@3
the user who created the access token was me
l
Have you revoked that token?
s
do the access tokens expire?
@little-cartoon-10569 not afaik
and unfortunately, we have to use user-based access tokens rather than an Org token b/c of the payment tier we’re in - I wish this weren’t the case
b
Okay well some steps to take: • verify the token is still valid • run a stack list against the project inside the action • Verify the stack name is correct
s
wait, it could be the user was removed from access - we have 2 separate monorepos (one for infra and one for apps). It may be the access token in the infra was from a previous user
how do I …?
run a stack list against the project inside the action
b
run pulumi stack ls as a job step
👍 1
s
it was the access token
🎉 1
thanks for jumping in so quickly @billowy-army-68599 @little-cartoon-10569 - greatly appreciate the help
👍 1
🎉 1
w
@square-laptop-45713 Very glad you got a resolution! 🥳 Would it be okay with you if I close the issue?
s
I closed it already @worried-rain-74420
w
Awesome, thanks!