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
0
Merge Requests
0
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
Kazuhiko Shiozaki
gitlab-ce
Commits
ec61dfdc
Commit
ec61dfdc
authored
Jun 26, 2014
by
Marvin Frick
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
adds rake task to clean up deleted LDAP users
parent
024e0577
Changes
1
Hide 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 @
ec61dfdc
...
@@ -84,5 +84,29 @@ namespace :gitlab do
...
@@ -84,5 +84,29 @@ namespace :gitlab do
puts
"To cleanup this directories run this command with REMOVE=true"
.
yellow
puts
"To cleanup this directories run this command with REMOVE=true"
.
yellow
end
end
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
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