fix(ec2): handle runner role output for v7.7.0#329
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fixes the EC2 runner deployment output after upgrading
github-aws-runners/terraform-aws-github-runnertov7.7.0.In
v7.7.0, the upstream runner IAM role is now returned as a counted resource, sorunner.role_runneris a tuple. Forge was still readingrunner.role_runner.arn, which caused Terraform/OpenTofu to fail with:This PR updates the EC2 runner ARN output to read
runner.role_runner[0].arn, updates the generated Terraform module docs, ignores local.ansible/cache files, and tightens the Forge subscription trust policy by removing direct EC2/S3 service-principal assume-role access.Type of Change
Checklist
Validation: pre-commit passed, including Terraform/OpenTofu formatting and validation.