Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
M
Metabase
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Engineering Digital Service
Metabase
Commits
5244c0d5
Unverified
Commit
5244c0d5
authored
4 years ago
by
Robert Roland
Committed by
GitHub
4 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Revert "Allow the Administrators group to sync (#13629)" (#13791)
This reverts commit
3e1dab30
.
parent
91f7ff76
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
src/metabase/integrations/common.clj
+2
-2
2 additions, 2 deletions
src/metabase/integrations/common.clj
test/metabase/integrations/common_test.clj
+59
-58
59 additions, 58 deletions
test/metabase/integrations/common_test.clj
with
61 additions
and
60 deletions
src/metabase/integrations/common.clj
+
2
−
2
View file @
5244c0d5
...
...
@@ -11,9 +11,9 @@
(
defn
sync-group-memberships!
"Update the PermissionsGroups a User belongs to, adding or deleting membership entries as needed so that Users is only
in `new-groups-or-ids`. Ignores special groups like `all-users`."
in `new-groups-or-ids`. Ignores special groups like
`admin` and
`all-users`."
[
user-or-id
new-groups-or-ids
]
(
let
[
special-group-ids
#
{(
u/get-id
(
group/all-users
))}
(
let
[
special-group-ids
#
{(
u/get-id
(
group/admin
))
(
u/get-id
(
group/all-users
))}
user-id
(
u/get-id
user-or-id
)
;; Get a set of Group IDs the user currently belongs to
current-group-ids
(
db/select-field
:group_id
PermissionsGroupMembership
...
...
This diff is collapsed.
Click to expand it.
test/metabase/integrations/common_test.clj
+
59
−
58
View file @
5244c0d5
(
ns
metabase.integrations.common-test
(
:require
[
clojure.test
:refer
:all
]
(
:require
[
expectations
:refer
[
expect
]
]
[
metabase.integrations.common
:as
integrations.common
]
[
metabase.models
[
permissions-group
:as
group
:refer
[
PermissionsGroup
]]
...
...
@@ -46,67 +46,68 @@
(
let
[[
user-binding
groups-or-ids-to-put-user-in
]
bindings
]
`
(
do-with-user-in-groups
(
fn
[
~
user-binding
]
~@
body
)
~
groups-or-ids-to-put-user-in
))))
(
deft
es
t
sync
-
group
s-test
(
testing
"does syncing group memberships leave existing memberships in place if nothing has changed?"
(
is
(
=
#
{
"All Users"
":metabase.integrations.common-test/group"
}
(
with-user-in-groups
[
group
{
:name
(
str
::group
)}
user
[
group
]]
(
integrations.common/sync-group-memberships!
user
#
{
group
})
(
group-memberships
user
)))
))
;; do
es sync
ing
group
memberships leave existing memberships in place if nothing has changed?
(
expect
#
{
"All Users"
":metabase.integrations.common-test/group"
}
(
with-user-in-groups
[
group
{
:name
(
str
::group
)}
user
[
group
]]
(
integrations.common/sync-group-memberships!
user
#
{
group
})
(
group-memberships
user
)))
(
testing
"the actual `PermissionsGroupMembership` object should not have been replaced"
(
with-user-in-groups
[
group
{
:name
(
str
::group
)}
user
[
group
]]
(
let
[
membership-id
#
(
db/select-one-id
PermissionsGroupMembership
:group_id
(
u/get-id
group
)
:user_id
(
u/get-id
user
))
original-membership-id
(
membership-id
)]
(
integrations.common/sync-group-memberships!
user
#
{
group
})
(
is
(
=
original-membership-id
(
membership-id
))))))
;; the actual `PermissionsGroupMembership` object should not have been replaced
(
expect
(
with-user-in-groups
[
group
{
:name
(
str
::group
)}
user
[
group
]]
(
let
[
membership-id
#
(
db/select-one-id
PermissionsGroupMembership
:group_id
(
u/get-id
group
)
:user_id
(
u/get-id
user
))
original-membership-id
(
membership-id
)]
(
integrations.common/sync-group-memberships!
user
#
{
group
})
(
=
original-membership-id
(
membership-id
)))))
(
testing
"does syncing group memberships add users to new groups correctly?"
(
is
(
=
#
{
":metabase.integrations.common-test/group-1"
":metabase.integrations.common-test/group-2"
"All Users"
}
(
with-user-in-groups
[
group-1
{
:name
(
str
::group-1
)}
group-2
{
:name
(
str
::group-2
)}
user
[
group-1
]]
(
integrations.common/sync-group-memberships!
user
#
{
group-1
group-2
})
(
group-memberships
user
)))))
;; does syncing group memberships add users to new groups correctly?
(
expect
#
{
":metabase.integrations.common-test/group-1"
":metabase.integrations.common-test/group-2"
"All Users"
}
(
with-user-in-groups
[
group-1
{
:name
(
str
::group-1
)}
group-2
{
:name
(
str
::group-2
)}
user
[
group-1
]]
(
integrations.common/sync-group-memberships!
user
#
{
group-1
group-2
})
(
group-memberships
user
)))
(
testing
"does syncing group memberships remove users from old groups correctly?"
(
is
(
=
#
{
"All Users"
}
(
with-user-in-groups
[
group-1
{
:name
(
str
::group-1
)}
group-2
{
:name
(
str
::group-2
)}
user
[
group-1
]]
(
integrations.common/sync-group-memberships!
user
#
{})
(
group-memberships
user
)))))
;; does syncing group memberships remove users from old groups correctly?
(
expect
#
{
"All Users"
}
(
with-user-in-groups
[
group-1
{
:name
(
str
::group-1
)}
group-2
{
:name
(
str
::group-2
)}
user
[
group-1
]]
(
integrations.common/sync-group-memberships!
user
#
{})
(
group-memberships
user
)))
(
testing
"does adding & removing at the same time work correctly?"
(
is
(
=
#
{
":metabase.integrations.common-test/group-2"
"All Users"
}
(
with-user-in-groups
[
group-1
{
:name
(
str
::group-1
)}
group-2
{
:name
(
str
::group-2
)}
user
[
group-1
]]
(
integrations.common/sync-group-memberships!
user
#
{
group-2
})
(
group-memberships
user
)))))
;; does adding & removing at the same time work correctly?
(
expect
#
{
":metabase.integrations.common-test/group-2"
"All Users"
}
(
with-user-in-groups
[
group-1
{
:name
(
str
::group-1
)}
group-2
{
:name
(
str
::group-2
)}
user
[
group-1
]]
(
integrations.common/sync-group-memberships!
user
#
{
group-2
})
(
group-memberships
user
)))
(
testing
"if we attempt to add a user to a group that doesn't exist, does the group sync complete for the other groups?"
(
is
(
=
#
{
"All Users"
":metabase.integrations.common-test/group"
}
(
with-user-in-groups
[
group
{
:name
(
str
::group
)}
user
[
group
]]
(
tu.log/suppress-output
(
integrations.common/sync-group-memberships!
user
[
Integer/MAX_VALUE
group
]))
(
group-memberships
user
)))))
;; if we attempt to add a user to a group that doesn't exist, does the group sync complete for the other groups?
(
testing
"are admins synced?"
(
is
(
=
#
{
"Administrators"
"All Users"
}
(
with-user-in-groups
[
user
]
(
integrations.common/sync-group-memberships!
user
[(
group/admin
)])
(
group-memberships
user
)))))
(
expect
#
{
"All Users"
":metabase.integrations.common-test/group"
}
(
with-user-in-groups
[
group
{
:name
(
str
::group
)}
user
[
group
]]
(
tu.log/suppress-output
(
integrations.common/sync-group-memberships!
user
[
Integer/MAX_VALUE
group
]))
(
group-memberships
user
)))
(
testing
"are administrators removed appropriately?"
(
is
(
=
#
{
"All Users"
}
(
with-user-in-groups
[
user
[(
group/admin
)]]
(
integrations.common/sync-group-memberships!
user
[])
(
group-memberships
user
))))))
;; are special groups like admin & all users ignored?
(
expect
#
{
"All Users"
}
(
with-user-in-groups
[
user
]
(
integrations.common/sync-group-memberships!
user
[(
group/admin
)])
(
group-memberships
user
)))
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment