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 |
||
---|---|---|
.. | ||
api | ||
assets | ||
backup | ||
banzai | ||
bitbucket | ||
bitbucket_server | ||
constraints | ||
container_registry | ||
declarative_policy | ||
flowdock | ||
generators/rails/post_deployment_migration | ||
gitaly | ||
gitlab | ||
google_api | ||
haml_lint | ||
json_web_token | ||
mattermost | ||
microsoft_teams | ||
object_storage | ||
omni_auth/strategies | ||
peek | ||
quality | ||
rouge | ||
rspec_flaky | ||
support | ||
system_check | ||
tasks | ||
after_commit_queue.rb | ||
backup.rb | ||
banzai.rb | ||
carrier_wave_string_file.rb | ||
declarative_policy.rb | ||
event_filter.rb | ||
expand_variables.rb | ||
extracts_path.rb | ||
feature.rb | ||
file_size_validator.rb | ||
forever.rb | ||
gitlab.rb | ||
gt_one_coercion.rb | ||
milestone_array.rb | ||
mysql_zero_date.rb | ||
static_model.rb | ||
system_check.rb | ||
unfold_form.rb | ||
uploaded_file.rb | ||
version_check.rb |