REST support for managing schedule inputs

Problem

We need to allow users to manage inputs for pipeline schedules like we do for pipeline variables: https://docs.gitlab.com/api/pipeline_schedules/#pipeline-schedule-variables

Proposal

Add inputs arguments to the REST endpoints for creating and updating pipeline schedules

  • Pipeline schedules create endpoint: https://docs.gitlab.com/api/pipeline_schedules/#create-a-new-pipeline-schedule
  • Pipeline schedules update endpoint: https://docs.gitlab.com/api/pipeline_schedules/#edit-a-pipeline-schedule

For implementation details showing how to create and update inputs on pipeline schedules, like at the GraphQL mutations:

  • PipelineScheduleCreate: https://gitlab.com/gitlab-org/gitlab/-/blob/fd479363e5e9338fb38b404dd0c1d60c71f9e92d/app/graphql/mutations/ci/pipeline_schedule/create.rb#L59
  • PipelineScheduleUpdate: https://gitlab.com/gitlab-org/gitlab/-/blob/abd4eb20c2fdfdf6ebe19e04f732c42bf83b774c/app/graphql/mutations/ci/pipeline_schedule/update.rb#L54
    • Note: use name and pipeline_schedule to fetch inputs for updating. Do not use id. We'll be removing the usage of id from the mutation in Update pipeline schedule inputs using name (not... (#526030 - closed) • Avielle Wolfe • 17.11

Notes

  • Changes should be gated by the ci_inputs_for_pipelines feature flag
Edited Mar 20, 2025 by Avielle Wolfe
Assignee Loading
Time tracking Loading