Changed Gitlab group sync API call

SonarQube
1

Hi,

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    • sonarqube 9.9 community
  • how is SonarQube deployed:
    • Helm, K8s
  • what are you trying to achieve
    • return to behavior of 8.9-LTS group synchronization
  • what have you tried so far to achieve this

can some one help on this issue we got after upgrade from 8.9-LTS to 9.9-LTS.

With this issue ([SONAR-15171] - Jira) the list of returned groups
for synchronization was reduced by adding min_access_level=10 to the Gitlab API call.

(server/sonar-auth-gitlab/src/main/java/org/sonar/auth/gitlab/GitLabRestClient.java)

8.9: API_SUFFIX + "/groups", scribe, accessToken, GsonGroup::parse);
->
9.9: API_SUFFIX + "/groups?min_access_level=10", scribe, accessToken, GsonGroup::parse);

This is now filtering out groups visible because of child sharing.

After migration from 8.9-LTS we are now facing an great issue with this change in our Gitlab permission setup and would like to switch back to the old behavior.

There was already a discussion (add option to enable group sync at parent level by Guimove · Pull Request #3281 · SonarSource/sonarqube · GitHub) with some proposed code changes to add an option switch
which led to this still open Sonarsource ticket ([SONAR-15674] - Jira).

Is there any chance that this will be realized?
Is there another way to return to the old behavior?

Thanks for any help in advance
Cheers

6

Hi @Hermanns

Thanks for your feedback. The fix is not trivial, and we need to investigate possible solutions. We do not have any timeline yet and will update the SONAR-15674 once fixed.

Thanks for your comprehension

1 Like