Geo: Filter S3-backed LFS objects

gitlab-org/gitlab-ee!2760 was just merged, but Geo will likely try to download all LFS objects even if they are stored in S3.

For now, we should just ignore S3-backed files. In the future, we may mirror these to another S3 site.

added lfs label

@nick.thomas Seems like something we should do in %10.1?

Since !2760 (merged) made it into %10.0 I feel that we should include the fix in %10.0 as well, but it depends a bit on the consequences of Geo's behaviour at current, and how hard it's going to be to recover from them.

I think it definitely needs appraisal, at least, in %10.0 so I'll assign it to that milestone for now.

changed milestone to %10.0

@dbalexandre you can evaluate whether leaving this until %10.1 will cause us significant problems? What will the migration, if any, look like?

assigned to @dbalexandre

mentioned in merge request !2889 (merged)

@nick.thomas Let's stick with 10.0 for this. It's an easy fix https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2889.

closed via merge request !2889 (merged)

mentioned in commit fd326fc3

Issue gitlab-org/gitlab-ee#415 already existed to cover synchronization of LFS objects on object storage. I've updated the description to reflect the current goals.

mentioned in commit bca43619