Pierre Guinoiseau

I'm encountering the same issue with v1.19.1 and 1.19.2, but oddly only in 1 out of the 5 pods in the cluster. Adding spaces after each comma fixed it too,...

@divyaac this is a slightly different error from the one that was fixed in v1.19.1 (which I also ran into when upgrading to v1.19.0 previously), maybe the fix was incomplete.

You need to remove and import them back instead: ```terraform removed { from = module.cloudflare_resources["0"].cloudflare_worker_route.route lifecycle { destroy = false } } import { id = "/" to = module.cloudflare_resources["0"].cloudflare_workers_route.route[0]...

@jamengual hi, any chance this could make it into the next release? It would be really helpful for us at GitLab, and for all GitLab users. 🙏🏻

> Thus I wonder if it would be easier to pass the logic in somehow via NewGitlabClient then be able to access it via g in (g *GitlabClient) GetTeamNamesForUser()`. That...

> I'm not sure why; NewGitlabClient() is only ever called once, in server/server.go, don't we have enough information at that point to know what all the possible groups that might...

> Your code does a further intersection, which is "all groups we might have policy around". Again, just making sure I understand the logic. Yes the logic is just that...

@dorian-tsorfy I'll try to have the patch updated this week. 🤞🏻

I have rebased/updated the diff but kept the same logic. While doing so, I remembered why I initially didn't opt for building the list of all groups when initialising the...

@lukemassa OK that sounds good, it will also need to grab all groups from all configured policy sets on init. I'll update this PR next month as I'll be mostly...