We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently when you create a GARM runner pool using garm-cli there is no option to attach an IAM role to it.
garm-cli pool create \ --os-type windows \ --os-arch amd64 \ --enabled=true \ --flavor t2.small \ --image ami-0d5f36b04ca291a9f \ --min-idle-runners 0 \ --repo 5b4f2fb0-3485-45d6-a6b3-545bad933df3 \ --tags aws,windows \ --provider-name aws
It would be nice to have the ability to add an IAM instance profile to the runners pool to avoid using AWS Access Keys.
Basic use cases would be to build an AMI using Packer or push a docker image to ECR.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Currently when you create a GARM runner pool using garm-cli there is no option to attach an IAM role to it.
It would be nice to have the ability to add an IAM instance profile to the runners pool to avoid using AWS Access Keys.
Basic use cases would be to build an AMI using Packer or push a docker image to ECR.
The text was updated successfully, but these errors were encountered: