-
Notifications
You must be signed in to change notification settings - Fork 628
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
Module is not compatible with the GovCloud region #1245
Comments
I assume we have hard coded this even on more places. Feel free to sugges an absraction in a PR. Thanks for taking the time to create an issue. |
@npalm Surprisingly, changing that single line was enough to make the module work in my GovCloud environment with GHES. I am using the root module, default KMS, and most of the standard options. I will be doing more testing with some of the more niche options to find other GovCloud incompatibilities. Once I'm satisfied with my hard-coded changes, I'll write up an abstraction for it (hopefully automated, but potentially with an input variable) and put up a PR. |
@aidan-mundy is you issue resolved? |
@npalm I havent found any additional issues in the module (related to GovCloud anyway). Haven't had the chance to throw up an MR for the issue I mentioned above, but I can do that in the next week or two. |
I believe that with the merge mentioned above, this issue can be resolved. |
Agreed, that merge appears to resolve the issue I had detected, as well as other potentially related issues. It appears this fell off my radar at some point, thanks for picking up the slack @jokreliable |
No worries - Took me a month to get back on my radar too.. 😄 -- Glad it helped! |
I will add more problems here as I find them, initial problem in my GovCloud journey is that the GovCloud region ARNs start with "arn:aws-us-gov:" and the module hardcodes ARNs as "arn:aws:". (A similar problem will cause this module to fail in the China regions)
terraform-aws-github-runner/modules/runners/policies-runner.tf
Line 29 in 1e6c8b0
The text was updated successfully, but these errors were encountered: