Skip to content

Impove documentation for storage requirements of GEI #45142

Description

@jessehouwing

Code of Conduct

What article on docs.github.com is affected?

Storage requirements are most extensively documented for GHES migrations:
https://docs.github.com/en/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud#step-4-set-up-blob-storage

There are details about Azure Storage networking in the BitBucket section, which are missing from the GHES section
https://docs.github.com/en/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/managing-access-for-a-migration-from-bitbucket-server#virtual-network-firewall-rules-for-azure-blob-storage-for-githubcom

And similar requirements apply to the upcoming GitLab migrations as well.

When using customer-owned storage on a bbs->ghe migration a DIFFERENT set of vnets need to be added to the storage firewall. Details are available through support.

https://github.com/githubpartners-community/community/discussions/1024#discussioncomment-13254544

https://docs.github.com/en/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/managing-access-for-a-migration-from-bitbucket-server#ip-ranges-for-ghecom

This applies to GHES->GHE and GL->GHE as well.

What part(s) of the article would you like to see updated?

Instead of duplicating this under 3 different product migration sections, it makes more sense to put this under a single doc.

I propose adding a shared section for all types of migrations and either add a new page alongside:

https://docs.github.com/en/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer

Or add the details to that exact page.

Or add a page under the troubleshooting section

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    contentThis issue or pull request belongs to the Docs Content teamtriageDo not begin working on this issue until triaged by the team

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions