-
Notifications
You must be signed in to change notification settings - Fork 93
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
Map Mannequins during migration #1316
Comments
Are you familiar with the generate-mannequin-csv and reclaim-mannequin commands? They let you do it in bulk, and if the target uses EMU you can add the —skip-invitation flag to skip the emails. |
Hey Dylan, Familiar with the EMU side but EMU isn't an option for us unfortunately, and I would argue a lot of Enterprises that use EMU still need a GHEC Enterprise as well due to needing to handle open source and other caveats that EMU doesn't support. My understanding is the commands you mention will still require non EMU enterprises have every individual user accept the reclaim email. Please let me know if I misunderstood that though! This is asking for functionality that existed in previous tooling, whether ECI, or the GraphQL endpoints that required a Services Engineer engagement in the past. Again, with GH Connect, the connection already exists that links on prem identities to GHEC identities, so I'm hoping y'all can tap into that to implement this. At the least, allowing for an optional flag to pass in a mapping.csv as you could in prior tools would be greatly appreciated. |
there is a --no-prompt flag which you can use
|
Where is this documented? Official docs don't seem to reference it |
Hey mate, the documentation doesn't have a ll the flags but if you run |
Description
As an enterprise customer, we have over 7000 engineers actively using GHES. Emailing all 7000 to re-attribute is toilsome, especially when we already have GH Connect enabled and all of the on-prem identities are already linked to GHEC identities.
Request to implement previous features from ECI and legacy import tooling that allowed mapping/matching of mannequins either through a
user.csv
or other mapping file DURING import, rather than having to re-attribute them all later to claim mannequins.The text was updated successfully, but these errors were encountered: