Peter Woodworth

I can see how this would be useful, thank you for the suggestion! We should be able to make a check for this pretty easily

This issue seems resolved (plus I don't think this is an issue with this action in the first place) so I'm going to close it. Thanks all who helped find...

Hey all, just to let you know if you're following this issue that #246 is in the process of being reviewed and it will hopefully be merged soon. Thanks for...

Thanks for all your help in this thread @mungojam, it's much appreciated! To recap, [AWS docs](https://docs.aws.amazon.com/en_en/IAM/latest/UserGuide/reference_policies_iam-condition-keys.html#condition-keys-wif) suggest that this is an AWS limitation in not checking the `actor` key. Hopefully...

Reopening for visibility, but more importantly to track that this issue is related to a limitation in AWS (maybe we can push this internally)

This could be a feature we implement, however since there's a workaround you can do as described in the above comment, I wouldn't want to implement this unless it's something...

This issue seems to be resolved. Please ping me or open a new issue with both the workflow file used and the error message if you are still encountering this...

Hey all, and thanks Daniel for the contribution, it's much appreciated. I'm going to close this for the reason stated in #459. Look forward to the next major version release...

There are a few things going on here. First, [the subject claim will be the environment](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#filtering-for-a-specific-environment) if one is specified, so you cannot filter by branch through `sub` if environment...

This action doesn't set the region as a secret in code like it does with the keys. Can you please share reproduction steps i.e. your workflow file @vesubramanian?