Greg Dubicki

Closing as fixed in [v3](https://github.com/gitlabform/gitlabform/releases/tag/v3.0.0).

We can start by checking if the the config is a valid YAML and provide friendly error messages with github.com/adrienverge/yamllint using a method mentioned in https://github.com/adrienverge/yamllint/issues/112 .

We have moved this forward a bit in [v2.9.0](https://github.com/gdubicki/gitlabform/releases/tag/v2.9.0) thanks to switching the YAML parser from PyYAML to ruamel.yaml that by default [disallows duplicate dict keys](https://yaml.readthedocs.io/en/latest/api.html#duplicate-keys). It is also wrapped...

Haven't seen this since #1 has been implemented. Closing it then.

Thanks @razumv ! I’ll try to reproduce it.

I was not able to reproduce it on the latest GitLab 13.5.1 with a simple test I added in https://github.com/egnyte/gitlabform/pull/131 . What GitLab and GitLabForm versions are you using, @razumv...

@jccl : please try using v2. v1 is not supported anymore. Generally I still cannot reproduce this issue with the latest v2.1 and latest stable Gitlab, see https://github.com/egnyte/gitlabform/runs/2978563292?check_suite_focus=true .

Thanks @owindsor ! This may allow me to reproduce it but I have a few more questions. What do you mean by "All projects failed, so I removed the key."?...

I have checked this and frankly I am surprised that the current trivial code works at all, dealing successfully with many kinds of edge cases that you can encounter with...

Can you please check if you still have this issue after upgrading to [v2.10.0](https://github.com/gdubicki/gitlabform/releases/tag/v2.10.0), @vchepkov / @FlorianLudwig / @jccl / @jocado / @razumv ?