d18ee3faad
A project can have the same `LfsObject` linked with up to three `LfsObjectsProject` records. Each of these records would be for a different repository, recorded in the `repository_type` property. The different repositories at time of writing are "project", "wiki", and "design". See https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/13894 This change exports the list of `repository_type`s as a JSON mapping of oid => repository_types, which are imported to recreate the correct `LfsObjectsProject` records. https://gitlab.com/gitlab-org/gitlab-ee/issues/11090
23 lines
655 B
Ruby
23 lines
655 B
Ruby
include ActionDispatch::TestProcess
|
|
|
|
FactoryBot.define do
|
|
factory :lfs_object do
|
|
sequence(:oid) { |n| "b68143e6463773b1b6c6fd009a76c32aeec041faff32ba2ed42fd7f708a%05x" % n }
|
|
size 499013
|
|
end
|
|
|
|
trait :with_file do
|
|
file { fixture_file_upload("spec/fixtures/dk.png", "`/png") }
|
|
end
|
|
|
|
# The uniqueness constraint means we can't use the correct OID for all LFS
|
|
# objects, so the test needs to decide which (if any) object gets it
|
|
trait :correct_oid do
|
|
oid 'b804383982bb89b00e828e3f44c038cc991d3d1768009fc39ba8e2c081b9fb75'
|
|
size 1062
|
|
end
|
|
|
|
trait :object_storage do
|
|
file_store { LfsObjectUploader::Store::REMOTE }
|
|
end
|
|
end
|