amimas

I did some test using Gitlab 15.11.13 docker image and 16.2.2 (latest). Created 2 projects using the UI (`project1`, and `project-archived`) and it just had the default branch protection out...

I recently ran into similar issue. It's not just isolated to branch protection setting while the project is archived. My config for the project was like this: ```yaml group1/project-foo: project:...

@admantium-sg , Are you able to test it out using latest version of gitlab? Wondering if the API behaviour changed/fixed in newer version of gitlab. Anyways, going to close this...

> GitLab inherits permissions downwards to descendant groups, it is sufficient to only add members to one group. Maybe I'm just mis-interpreting this. But just to clarify, subgroups will always...

You could configure members on the 2nd level. For example: A/1 A/B A/C You can configure the "vip" user to only A/1. There's also a `inherit: false` config in gitlabform...

> Since you can't break inheritance on users we assign them at the project level not on groups. It has taken a while but we're almost free of group-level users...

The `inherit` key is a gitlabform feature for controlling the final/effective config that is generated for gitlabform. I don't think the above config will work. Currently to configure settings/members for...

Based on this thread, it seems there is already built-in retry logic when the API call fails with 500 server error. https://github.com/gitlabform/gitlabform/issues/531 Not sure what the issue is in your...

@felsgaertner - thanks for bringing this up. Since it's a gitlab issue, going to close it. Feel free to reopen it if I misunderstood.

Yes that can be useful. Do you have any suggestion for the config syntax? Will you be able to help contribute this feature?