Mohamed Habib

I think I have seen this behaviour before. Not sure why AWS sts client does not set a default region while setting a role. Need to dig further into it.

This might be a misconfiguration in the workflow itself. Out of curiousity you could try to do it with setup-aws: true in the digger step, since there might be some...

well, you might wanna try the version I'm about to release since it has an aws v1 to v2 upgrade so might help

it would help for repo if you shared workflow and simple digger yml

I can take a look at this, is there any steps that can help me reproduce this scenario? Its probably a case of digger bailing early but not updaing the...

Hey @JoshuaJackson-jobvite thanks a lot for this contribution ! This seems like an elegant solution and I think it would be great to have in our composite action Would love...

Hey @evanstachowiak thanks for chiming in! To be honest there is a solution that has a PR pending here for general plan and apply failures: #1579 Regarding things like failure...

@evanstachowiak in fact it does know the id of the job not when it first fires it (github api does not return the ID on workflow dispatch), we have to...

Hey @JoshuaJackson-jobvite sorry got carried away with a big feature we are cooking. Once that's done in the next couple of days I will get around to this. It has...

Thanks for the report, we need to handle this case of failed locking to update the job with an appropriate status