API call users.list(exclude_external=True) filters out wrong users
#3113
Replies: 2 comments 2 replies
-
|
Maybe this is an issue with GitLab? Is there a reason you believe the issue is with python-gitlab? |
Beta Was this translation helpful? Give feedback.
-
|
Could be an issue with GitLab. I'm honestly just curious if this is the standard behavior now, since there is no possibility to get support as a free user. |
Beta Was this translation helpful? Give feedback.
-
|
You are allowed to file an issue on GitLab. https://gitlab.com/gitlab-org/gitlab/-/issues And also search to see if the issue has been reported. |
Beta Was this translation helpful? Give feedback.
-
|
FYI: GitLab issue created by @johannes-michael https://gitlab.com/gitlab-org/gitlab/-/issues/516083 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I recently updated to 17.8 and the behavior of filtering internal/external users does not work properly.
We are on self-managed GitLab free EE. Newly registered users are automatically flagged as external, except when their email matches a specific regex (admin settings > account and limit).
Prior to the update, new users got the attribute
external=trueand people matching the regex gotexternal=false. Now after the update, people matching the regex getexternal=null. I'm not sure when that behavior changed.The problem now is, that an API call like
gl.users.list(exclude_external=True)for some reason filters out accounts both withexternal=trueandexternal=null, basically rendering it useless. Older accounts where the flag is stillexternal=falsework as expected.Any ideas what's going on?
Beta Was this translation helpful? Give feedback.
All reactions