amimas

@gosoly - Thanks for checking and glad to hear that by removing the `skip_group`, now it's not failing or giving you the original issue. Not too sure about the logging...

> in `_merge_configs` in `core.py` it merges together the group and project level settings with project winning if there is a more specific configuration of the same implementation > I...

@TimKnight-DWP - Thanks for confirming. Glad we're on the same page. Based on my explanation, I'd say you're simply seeing existing behaviour of gitlabform. It's not a new bug and...

Thanks for reporting it. Will you be able to help contribute this feature? If yes, let's discuss the config syntax and necessary logic for implementing it.

Thanks for chiming in @tmeijn and sharing the detail. I didn't look at gitlab's API closely, but if it's working in your case, that's thanks to GitLabForm's ["raw parameter passing"](https://gitlabform.github.io/gitlabform/reference/#raw-parameters-passing)...

I haven't had a chance to investigate this, but I agree with what you're expecting. Unfortunately, this processor is still using a common logic (`MultipleEntitiesProcessor`) used before we started using...

Looking at the error message you're getting, it seems misleading. ``` * (1/1) Processing project: mygroup/myproject Error: Entity mybadge in badges for mygroup/myproject doesn't have some of its keys required...

Seems this issue is same as #684 since both badge and variables extends the `MultipleEntitiesProcessor`. Is the main issue that `delete` config is attempting to create instead of delete?

Sorry for the late reply @weakcamel. Been busy with work. Feel free to open a PR with your suggestion and some relevant tests. I think you're proposing to update the...

What happens when you try to use that config? Any error?