Feature Request - Ability to take ownership of gitlab_pipeline_schedule
This is related to gitlab#20762 .
I'm missing the ability for the current user to take ownership of a pipeline schedule. This would allow my team to ensure that deactivated users are not the owners of important pipeline schedules.
Alternatively, it might be interesting to be able to specify the owner directly.
I envision something like the following:
resource "gitlab_pipeline_schedule" "example" {
project = "12345"
description = "Used to schedule builds"
ref = "master"
cron = "0 1 * * *"
take_ownership = true
}
Would a Merge Request for this feature be interesting?
Related GitLab APIs
API documentation: https://docs.gitlab.com/ee/api/pipeline_schedules.html#take-ownership-of-a-pipeline-schedule
Additional Details
-
GitLab REST API resources available (read for data sources, crud for resources) -
go-gitlab
does support the related GitLab API already -
I'd like to contribute it myself