GitHub Enterprise Importer (GEI) Demo

Поділитися
Вставка
  • Опубліковано 10 вер 2024
  • In this video I use the GitHub Enterprise Importer (gei) to migrate an Org from GHES to GHEC/EMU.
    Prereq's would be the Git (git), GitHub CLI (gh), the GEI module/plugin (gei), Powershell, for GHES, I'll also need an Azure Storage Account.
    Note: At time 11:41 you'll notice that 2 Actions workflows didn't migrate - the first one is an invalid action workflow as it starts with "./gihub/workflow... ", the second is Dependabot's workflow which is automated by enabling Dependabot. This is expected and not an error.
    Steps can be found on GitHub: github.com/ocp...
    Documentation
    Obtaining GEI : docs.github.co...
    Reclaiming "mannequins" : docs.github.co...
    GitHub Enterprise Managed Users (EMU) : docs.github.co...

КОМЕНТАРІ • 8

  • @slidemx5384
    @slidemx5384 Рік тому

    Great video @OCPDude!

  • @user-cc8le3rm2y
    @user-cc8le3rm2y Рік тому

    Hey OCPdude, great demo video. Helped a lot. I have couple of questions.
    1. If I have thousands of users, I will have to manually update that "mannequin.csv" files to match in the destination? Can GEI or any other tool help me migrate users from source (GHES/GHEC) to GHEC+EMU using IdP like Azure AD or Octa?
    2. Do you have any demo video of repo-by-repo migration using GEI?

    • @OCPdude
      @OCPdude  Рік тому

      Thank you for your questions. I haven't done any videos in awhile,I should get back on this. 😀
      1. if you are on GHEC with AAD/Okta integration already, those users will map to the same IdP on GHEC+EMU. For GHES... say LDAP to GHEC(+EMU) w/ AAD/Okta integration, unfortunately managing the user mappings may be a pain. I am not familiar with an easy way to remap user identities, but since users map via their email addresses... if those are the same with LDAP & AAD/Okta, I believe they should align without the need for mannequins. I haven't tested this myself.
      2. For a repo-to-repo migration, you could just use the import function GHEC -> GHEC+EMU, or use GEI and then edit your migration script to only include those repo's you wish to migrate. The GEI script would work the same for GHEC as it would for GHES.

    • @user-cc8le3rm2y
      @user-cc8le3rm2y Рік тому

      @@OCPdude thanks for your quick response. appreciate it. I am in GHEC and using Azure AD with SAML today. Need to migrate to GHEC+EMU. So migrating Org or Repo level using GEI, I will have mannequin users that I will need to reattribute. Got it. Thanks again.

    • @OCPdude
      @OCPdude  Рік тому +1

      @@user-cc8le3rm2y Since GitHub connects users by email addresses, if you're using the same IdP for each environment - you may not have to deal with mannequins at all.

    • @user-cc8le3rm2y
      @user-cc8le3rm2y Рік тому

      @@OCPdude That'd be great. Thanks!

  • @greentealotus8840
    @greentealotus8840 Рік тому

    Hi great demo, can you please make a video on the GEI installation part as well? is it a local installation or on github server?

    • @OCPdude
      @OCPdude  Рік тому +2

      It’s local, and a module add on to the gh CLI. It’s easy to install following the documentation in the GEI links provided.