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
48 lines
1.5 KiB
Ruby
48 lines
1.5 KiB
Ruby
# frozen_string_literal: true
|
|
|
|
module Gitlab
|
|
module GitalyClient
|
|
class ObjectPoolService
|
|
attr_reader :object_pool, :storage
|
|
|
|
def initialize(object_pool)
|
|
@object_pool = object_pool.gitaly_object_pool
|
|
@storage = object_pool.storage
|
|
end
|
|
|
|
def create(repository)
|
|
request = Gitaly::CreateObjectPoolRequest.new(
|
|
object_pool: object_pool,
|
|
origin: repository.gitaly_repository)
|
|
|
|
GitalyClient.call(storage, :object_pool_service, :create_object_pool, request)
|
|
end
|
|
|
|
def delete
|
|
request = Gitaly::DeleteObjectPoolRequest.new(object_pool: object_pool)
|
|
|
|
GitalyClient.call(storage, :object_pool_service, :delete_object_pool, request)
|
|
end
|
|
|
|
def link_repository(repository)
|
|
request = Gitaly::LinkRepositoryToObjectPoolRequest.new(
|
|
object_pool: object_pool,
|
|
repository: repository.gitaly_repository
|
|
)
|
|
|
|
GitalyClient.call(storage, :object_pool_service, :link_repository_to_object_pool,
|
|
request, timeout: GitalyClient.fast_timeout)
|
|
end
|
|
|
|
def unlink_repository(repository)
|
|
request = Gitaly::UnlinkRepositoryFromObjectPoolRequest.new(
|
|
object_pool: object_pool,
|
|
repository: repository.gitaly_repository
|
|
)
|
|
|
|
GitalyClient.call(storage, :object_pool_service, :unlink_repository_from_object_pool,
|
|
request, timeout: GitalyClient.fast_timeout)
|
|
end
|
|
end
|
|
end
|
|
end
|