debian-mirror-gitlab/data/deprecations/14-8-runner-api-status-filter-does-accept-active-or-paused.yml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

19 lines
1.1 KiB
YAML
Raw Normal View History

2022-04-04 11:22:00 +05:30
- name: "REST API Runner will not accept `status` filter values of `active` or `paused`"
2022-05-07 20:08:51 +05:30
announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated.
2022-04-04 11:22:00 +05:30
announcement_date: "2022-02-22"
removal_milestone: "16.0"
removal_date: "2023-04-22"
breaking_change: true
2022-05-07 20:08:51 +05:30
body: | # Do not modify this line, instead modify the lines below.
2022-04-04 11:22:00 +05:30
The GitLab Runner REST endpoints will stop accepting `paused` or `active` as a status value in GitLab 16.0.
A runner's status will only relate to runner contact status, such as: `online`, `offline`.
Status values `paused` or `active` will no longer be accepted and will be replaced by the `paused` query parameter.
When checking for paused runners, API users are advised to specify `paused=true` as the query parameter.
When checking for active runners, specify `paused=false`.
stage: Verify
tiers: [Core, Premium, Ultimate]
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/351109
2022-07-16 23:28:13 +05:30
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#queryrunners