Nick Alteen
Nick Alteen
Current workaround: 1. Create new session credentials by running `aws sts get-session-token`. ```bash aws sts get-session-token \ --serial-number MFA_DEVICE_ARN \ --token-code MFA_DEVICE_TOKEN \ --profile mfauser ``` 1. Create a separate...
I would imagine automated/headless situations would not be configured to use IAM users that require MFA. The AWS-recommended approach would be to use an IAM instance profile, for example. The...
This should also be addressed in #296 :)
This should be resolved by #296 :)
This should be resolved by #296 :)
This should be resolved by #296 :) The PR converts the action to a TypeScript action instead of using a container.
Apologies, I am going to close this PR as there is a large refactor of this repo in progress. The licenses will be replaced as part of this change.
This should be fixed in #296 :)
Note: CI is going to fail as this workflow does not exist on `main`, hence additional permissions will not be available
This should be fixed by #296 :) This approach uses GraphQL instead of the REST API, which will let you filter by the type (issue/PR) and creator.