Skip to content

fix: Add prefix to the policies which breaks multi runner configuration #4341

New issue

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

Closed

Conversation

prashanthbgoud
Copy link
Contributor

No description provided.

@prashanthbgoud prashanthbgoud changed the title Fix: Add prefix to the policies which breaks multi runner configuration fix: Add prefix to the policies which breaks multi runner configuration Jan 7, 2025
@prashanthbgoud
Copy link
Contributor Author

@npalm could you review?

Copy link
Member

@npalm npalm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please explain why you adding the prefix, the aws_iam_role_policy is adding inline policies to a role. Which means no need to prefix per environment. As long the role is unqique there will be no clash.

@prashanthbgoud
Copy link
Contributor Author

we use https://github.com/philips-labs/terraform-aws-github-runner/tree/main/modules/multi-runner, I see there are some policies for scaleup and scaledown which are created per runner config. if we have a multi-runner config, it creates policies with the same name multiple times.

@npalm
Copy link
Member

npalm commented Jan 9, 2025

we use https://github.com/philips-labs/terraform-aws-github-runner/tree/main/modules/multi-runner, I see there are some policies for scaleup and scaledown which are created per runner config. if we have a multi-runner config, it creates policies with the same name multiple times.

The module (multi-runner) creates roles and inside the roles customer managed inline policies. Those policies only exists inside a role. The role already have the prefix.

See here an example of a lambda role (scale-up)
image

@prashanthbgoud
Copy link
Contributor Author

Thanks for clarifying, I will close the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants