Armin Gerten

In order to move this forward, it could be considered to provide a [JSON Schema](https://json-schema.org/) that describes the basic structure of the `config.yml` file. Providing such schema has multiple advantages:...

> One work-around could be yaml anchors. You can move the shared configs into one or more yaml anchor and then apply them wherever needed. That is true in terms...

> We will take it into consideration when designing v4 of the app, but I cannot commit to any deadlines for it, sorry (see #343 for more info). Thanks @gdubicki...

> But I am not sure if I completely understand how it would be used so can you please provide a semi-complete usage example, @armingerten? I mean a config where...

> One of the unclear to me things is that in the GitLab API projects can have topics assigned (there is "topics" attribute listed [here](https://docs.gitlab.com/ee/api/projects.html#edit-project)), but groups cannot (no "topics"...

@jimisola @amimas Thanks for all the input and suggestion. I really like how this idea is evolving! > There could also be use case to restrict the above to certain...

I started to structure my configuration using multiple `config_*.yml` files already. If GitLabForm allowed multiple config files via `-c` parameter, I'd be very happy. 😉 Currently I am using the...

Yes, I also faced that problem when merging multiple files using `yq`. I ended up just sorting the keys on the root level of my YAML file by altering the...

> The only feature we were originally targeting as part of the first alpha that did not make it was `kubectl diff` support. The featureset in `kubectl apply` is complete...

This seems to be related / a duplicate of [!123](https://github.com/mvisonneau/gitlab-ci-pipelines-exporter/issues/123)