amimas

Thanks for the suggestion @philippe-granet . In addition to `max_retries`, maybe `obey_rate_limit` should be configurable? > If you don't want to wait, you can disable the rate-limiting feature, by supplying...

I think there's a lot of places that are currently not handled by the dry-run option. It's very basic at the moment. Instead of handling this case by case like...

Thanks for raising this. Historically gitlabform was intended for managing project and group settings only. That's why `project_and_groups` key is required. Being able to manage GitLab server's setting is a...

Hi @margana - Thanks for the report and doing all the investigation. It'd be good to provide some more context of the issue before going into the solution (e.g. sample...

Thanks. As requested, could you please share your gitlabform config?

@BenediktBertsch - Thanks for helping with gitlabform development. I haven't had time to review this PR. But wanted to drop this note here for attention. I had a chance to...

> Not quite sure how to write tests that are covering both cases... should I create a matrix for it and run two versions of gitlab then via GitHub actions...

Good question @gosoly . I think there are 2 parts to it. > Is there a way we could detect this in dry-run mode I'm not sure there's a way...

Hi @hiaik - Contribution is always welcome. I do have some thoughts before that is continued though. Would love to get feedbacks. First, let's address the issue with a jump...

> Not sure tbh how we can orchestrate effective configuration created by gitlabform (specifically for my request: when gitlabform generates, for example, 400 projects config -> numbered it 1..400 ->...