migrate externally hosted git-lfs objects into GitLab

Topic to Evaluate

Customers may be using a non-GitLab solution to store Git LFS objects.

For example, Artifactory supports this.

• their quick start guide
• their detailed docs

It involves adding a .lfsconfig to the repo

[lfs]
   url = "https://lfsremote:8080/api/lfs/project"

This was raised in a support ticket. (GitLab team members read more in the ticket and SF) Customers seeking to simplify their environment may want to consolidate git-lfs into GitLab.

Purpose of this issue is to assemble a procedure for achieving this.

related:

• #29967

High level

• create a feature branch on a client that has git-lfs installed and working
• remove the .lfsconfig
• push this to GitLab along with the LFS objects
• merge to the main branch.

It's not that different from pushing an existing repository hosted on GitLab server 'A' to GitLab server 'B'.

Detail

To follow.

To do

• LFS objects not currently on the main branch?
• Other feature branches? A server hook to ensure .lfsconfig is not pushed? Seems like it'd be an update hook rather than a pre-receive hook

Tasks to Evaluate

• Determine feasibility of the feature
• Create issue for implementation or update existing implementation issue description with implementation proposal
• Set weight on implementation issue
• If weight is greater than 5, break issue into smaller issues
• Add task
• Add task

Risks and Implementation Considerations