Skip to content
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

feat: PR to Support GitHub Enterprise Cloud with Data Residency #4367

Merged
merged 11 commits into from
Jan 28, 2025

Conversation

neethu-p
Copy link
Contributor

@neethu-p neethu-p commented Jan 17, 2025

Hello team,
This PR is raised to enhance the module’s functionality to support GitHub Enterprise Cloud with data residency.
Reference issue - #4364

Below are the details of the changes:

  1. The PR introduces support for GitHub Enterprise Cloud instances hosted on a dedicated subdomain of ghe.com, in addition to the current handling of github.com and GHES.

2.The primary difference between github.com and ghe.com is the API access URL. While github.com uses https://api.github.com, GHE Cloud instances use the format https://api.companyname.ghe.com.

  1. To accommodate this, I have utilised the existing ghes_url parameter. The new ghe.com URL can be passed to this parameter for smooth integration.

  2. This change has been thoroughly tested across all GitHub instances: GHES, github.com, and ghe.com, ensuring compatibility and reliability.
    Please review the PR and let me know if you have any feedback or suggestions.

@neethu-p neethu-p requested review from a team as code owners January 17, 2025 12:37
@neethu-p neethu-p changed the title PR to Support GitHub Enterprise Cloud with Data Residency feat: PR to Support GitHub Enterprise Cloud with Data Residency Jan 17, 2025
Copy link
Contributor

@jervi jervi left a comment

Choose a reason for hiding this comment

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

Just some nitpicking - but there's a chance that the tests for ghe.com gives a false positive (e.g. fooghe.com) - it's safer to include the preceding period.

README.md Outdated Show resolved Hide resolved
@npalm npalm self-requested a review January 20, 2025 12:46
@npalm
Copy link
Member

npalm commented Jan 20, 2025

Great to see the work is done to support GH enterprise cloud. Not time to review the PR yet. But do you also see any chance to adjust docs and make clear GHES configuraiton also support enterprise cloud.

@neethu-p
Copy link
Contributor Author

Yes, the docs and README files are updated accordingly. Kindly have a look

@neethu-p
Copy link
Contributor Author

Hello @npalm Have you got a chance to review the PR ?

@npalm
Copy link
Member

npalm commented Jan 24, 2025

Sorry this week was too busy. Will check the PR asap. Thanks for all the support on GHEC

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.

@neethu-p took a bit of time to review. Looks good made a view tiny remarks. Will test the change as well, will update the PR comments once done.

modules/multi-runner/README.md Show resolved Hide resolved
modules/runners/README.md Show resolved Hide resolved
@npalm
Copy link
Member

npalm commented Jan 27, 2025

Tested a deployment for both pool and scale-up. All working as epxtected

@neethu-p
Copy link
Contributor Author

@npalm The review comments are addressed!

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.

Thanks for your contribution.

@npalm npalm merged commit e5ebd5f into github-aws-runners:main Jan 28, 2025
1 check passed
npalm added a commit that referenced this pull request Jan 28, 2025
@npalm
Copy link
Member

npalm commented Jan 28, 2025

@neethu-p]reverting the PR since the ci is borken, strange it should break on the PR:
https://github.com/github-aws-runners/terraform-aws-github-runner/actions/runs/13007945341/job/36278943305

@npalm
Copy link
Member

npalm commented Jan 28, 2025

@neethu-p please can you re-create the PR, soe we can see how we can fix the CI?

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.

3 participants