At the moment, nope. The api is fairly simple https://docs.gitlab.com/ee/api/status_checks.html#create-external-status-check-service

So I'm thinking something like
external_status_checks:
  - name:
    url:
    branches:
      - 

Would the following make sense for the syntax by putting the config under existing project object?

project:
  external_status_checks:
    <name-of-service>:
      url: ...

Under <name-of-service>, I think rest of the parameter should follow Gitlab's API. It should take advantage of GitlabForm's raw parameter passing design/architecture. And I used <name-of-service> to follow branch protection, pipeline schedule, etc instead of having name as a separate config key.

I'm suggesting to put the new config under project just because I'm not sure if the new config needs to be another top level key/object. Unfortunately other "CI related" settings/configs are under project_settings but having this new one under that might be confusing. So, I thought grouping it under project is probably the closest pattern. Currently top level configs in gitlabform don't really represent a gitlab feature. This might also require tweak to "inheritance breaking" if a new top level config is added (i'm not sure).

One other suggestion I might add is to include the support for enforce as well. I guess this could be implemented separately but it's probably easier to do it at the same time as this feature being implemented since one would have access to the gitlab license for testing anyways.

Or similar.

However... it isn't supported in python-gitlab yet (ref python-gitlab/python-gitlab#2632) so might need to look at that first if you're wanting to move to that for the interface?

I don't think using python-gitlab would be a requirement. We need more contributors to help moving existing codes of gitlabform to use python-gitlab. I imaging it might take awhile.

Add Support for External Status Checks #583

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions