Validating a CI yaml file with include keyword on the API fails
When trying to validate the content of a .gitlab-ci.yml
file via the API (POST /api/v4/ci/lint
), if the content of the configuration containts a top-level include:
keyword, then the API returns an error.
The following error is returned by the API: "jobs:include config should be a hash"
.
In the point of view of the user, even if the content of the include
d file is not checked, the configuration looks valid.
Within the API CI lint endpoint we can't have context over the project scope (as opposed to the CI file validation within a project). Thus I think the API should validate the content of the include:
keyword too.