Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
c8ac0ab3
Commit
c8ac0ab3
authored
Jul 04, 2014
by
Dmitriy Zaporozhets
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #7208 from MrMarvin/ce_rake_cleanup_ldap_users
Adds rake task to clean up deleted LDAP users
parents
d8f4c363
ec61dfdc
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
24 additions
and
0 deletions
+24
-0
lib/tasks/gitlab/cleanup.rake
lib/tasks/gitlab/cleanup.rake
+24
-0
No files found.
lib/tasks/gitlab/cleanup.rake
View file @
c8ac0ab3
...
...
@@ -84,5 +84,29 @@ namespace :gitlab do
puts
"To cleanup this directories run this command with REMOVE=true"
.
yellow
end
end
desc
"GITLAB | Cleanup | Block users that have been removed in LDAP"
task
block_removed_ldap_users: :environment
do
warn_user_is_not_gitlab
block_flag
=
ENV
[
'BLOCK'
]
User
.
ldap
.
each
do
|
ldap_user
|
print
"
#{
ldap_user
.
name
}
(
#{
ldap_user
.
extern_uid
}
) ..."
if
Gitlab
::
LDAP
::
Access
.
open
{
|
access
|
access
.
allowed?
(
ldap_user
)
}
puts
" [OK]"
.
green
else
if
block_flag
ldap_user
.
block!
puts
" [BLOCKED]"
.
red
else
puts
" [NOT IN LDAP]"
.
yellow
end
end
end
unless
block_flag
puts
"To block these users run this command with BLOCK=true"
.
yellow
end
end
end
end
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment