amimas

@hiaik - after a bit more digging trying to reproduce the issue, I realized that it only happens when new users are being created and then they are being referenced...

The above mentioned change has been merged and released in [v4.0.3](https://github.com/gitlabform/gitlabform/releases/tag/v4.0.3). @hiaik - Please try it. I'd expect your execution time to drop back to prior to v4.0.1. @TimKnight-DWP -...

I don't think that should be a problem. The key name having spaces is already allowed in Yaml. For example, below is an example of how GitLabForm uses that for...

Thanks for the suggestion. In your case, I think you can optimize the config using yaml's anchor/alias feature. ```yaml projects_and_groups: # Define base approval rule with anchor _default_rule: &default_rule approvals_required:...

I might not be understanding the intended setup. From your sample config, it seems you're trying to share a subgroup with a parent group? Can that even be done in...

> oh I forgot to mention that have we user groups only hierarchy built under the path `company_root/groups` and we set that group with `group_members:inherit:false` so it won't be inheriting...

gitlabform is designed using configuration hierarchy pattern. Config defined in parent level is applied to the child level resources (projects or groups) by first generating an effective configuration for each...

Thanks for reporting @tmeijn . Is this a recent issue - maybe after upgrading either gitlab or gitlabform? Or, did you have group names in upper case before? Curious if...

Hi @tmeijn . Thanks for the context. I haven't had a chance to investigate this yet. Will you be able to help with this issue? I'd suggest adding a unit...

> Would it be possible to either ignore a protected branch if it the list in protected_branches: is > 1, or completely ignore any missing branches if that's easier? I...