752e9c18a1
This action doesn't lean on reduplication, so a short call can me made to the Gitaly server to have the object pool remove its remote to the project pending deletion. https://gitlab.com/gitlab-org/gitaly/blob/f6cd55357/internal/git/objectpool/link.go#L58 When an object pool doesn't have members, this would invalidate the need for a pool. So when a project leaves the pool, the pool will be destroyed on the background. Fixes: https://gitlab.com/gitlab-org/gitaly/issues/1415
47 lines
1.3 KiB
Ruby
47 lines
1.3 KiB
Ruby
# frozen_string_literal: true
|
|
|
|
require 'spec_helper'
|
|
|
|
describe PoolRepository do
|
|
describe 'associations' do
|
|
it { is_expected.to belong_to(:shard) }
|
|
it { is_expected.to have_one(:source_project) }
|
|
it { is_expected.to have_many(:member_projects) }
|
|
end
|
|
|
|
describe 'validations' do
|
|
let!(:pool_repository) { create(:pool_repository) }
|
|
|
|
it { is_expected.to validate_presence_of(:shard) }
|
|
it { is_expected.to validate_presence_of(:source_project) }
|
|
end
|
|
|
|
describe '#disk_path' do
|
|
it 'sets the hashed disk_path' do
|
|
pool = create(:pool_repository)
|
|
|
|
expect(pool.disk_path).to match(%r{\A@pools/\h{2}/\h{2}/\h{64}})
|
|
end
|
|
end
|
|
|
|
describe '#unlink_repository' do
|
|
let(:pool) { create(:pool_repository, :ready) }
|
|
|
|
context 'when the last member leaves' do
|
|
it 'schedules pool removal' do
|
|
expect(::ObjectPool::DestroyWorker).to receive(:perform_async).with(pool.id).and_call_original
|
|
|
|
pool.unlink_repository(pool.source_project.repository)
|
|
end
|
|
end
|
|
|
|
context 'when the second member leaves' do
|
|
it 'does not schedule pool removal' do
|
|
create(:project, :repository, pool_repository: pool)
|
|
expect(::ObjectPool::DestroyWorker).not_to receive(:perform_async).with(pool.id)
|
|
|
|
pool.unlink_repository(pool.source_project.repository)
|
|
end
|
|
end
|
|
end
|
|
end
|