gitlab-org--gitlab-foss/app/workers/delete_user_worker.rb

class DeleteUserWorker
  include Sidekiq::Worker
  include DedicatedSidekiqQueue

  def perform(current_user_id, delete_user_id, options = {})
    delete_user  = User.find(delete_user_id)
    current_user = User.find(current_user_id)

    Users::DestroyService.new(current_user).execute(delete_user, options.symbolize_keys)
  rescue Gitlab::Access::AccessDeniedError => e
    Rails.logger.warn("User could not be destroyed: #{e}")
  end
end
A worker deletes a user, so the request doesn't time out Fixes #13261 2016-02-17 08:41:33 -05:00			`class DeleteUserWorker`
			`include Sidekiq::Worker`
Re-organize queues to use for Sidekiq Dumping too many jobs in the same queue (e.g. the "default" queue) is a dangerous setup. Jobs that take a long time to process can effectively block any other work from being performed given there are enough of these jobs. Furthermore it becomes harder to monitor the jobs as a single queue could contain jobs for different workers. In such a setup the only reliable way of getting counts per job is to iterate over all jobs in a queue, which is a rather time consuming process. By using separate queues for various workers we have better control over throughput, we can add weight to queues, and we can monitor queues better. Some workers still use the same queue whenever their work is related. For example, the various CI pipeline workers use the same "pipeline" queue. This commit includes a Rails migration that moves Sidekiq jobs from the old queues to the new ones. This migration also takes care of doing the inverse if ever needed. This does require downtime as otherwise new jobs could be scheduled in the old queues after this migration completes. This commit also includes an RSpec test that blacklists the use of the "default" queue and ensures cron workers use the "cronjob" queue. Fixes gitlab-org/gitlab-ce#23370 2016-10-21 12:13:41 -04:00			`include DedicatedSidekiqQueue`
A worker deletes a user, so the request doesn't time out Fixes #13261 2016-02-17 08:41:33 -05:00
Add ability to delete a user with force 2016-02-25 03:20:28 -05:00			`def perform(current_user_id, delete_user_id, options = {})`
A worker deletes a user, so the request doesn't time out Fixes #13261 2016-02-17 08:41:33 -05:00			`delete_user = User.find(delete_user_id)`
			`current_user = User.find(current_user_id)`

Fix inconsistent naming for services that delete things * Changed name of delete_user_service and worker to destroy * Move and change delete_group_service to Groups::DestroyService * Rename Notes::DeleteService to Notes::DestroyService 2016-08-13 08:45:31 -04:00			`Users::DestroyService.new(current_user).execute(delete_user, options.symbolize_keys)`
Add user deletion permission check in `Users::DestroyService` We saw from a recent incident that the `Users::DestroyService` would attempt to delete a user over and over. Revoking the permissions from the current user did not help. We should ensure that the current user does, in fact, have permissions to delete the user. Signed-off-by: Rémy Coutable <remy@rymai.me> 2017-02-04 03:14:17 -05:00			`rescue Gitlab::Access::AccessDeniedError => e`
			`Rails.logger.warn("User could not be destroyed: #{e}")`
A worker deletes a user, so the request doesn't time out Fixes #13261 2016-02-17 08:41:33 -05:00			`end`
			`end`