debian-mirror-gitlab/data/deprecations/14-5-runner-api-status-does-contain-paused.yml

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

20 lines
1.2 KiB
YAML
Raw Normal View History

2022-11-25 23:54:43 +05:30
- name: "GraphQL API Runner status will not return `paused`"
2022-05-07 20:08:51 +05:30
announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
2022-03-02 08:16:31 +05:30
announcement_date: "2021-11-22"
2022-06-21 17:19:12 +05:30
removal_milestone: "16.0" # the milestone when this feature is planned to be removed
removal_date: "2023-04-22" # the date of the milestone release when this feature is planned to be removed
2022-03-02 08:16:31 +05:30
breaking_change: true
2022-05-07 20:08:51 +05:30
body: | # Do not modify this line, instead modify the lines below.
2022-11-25 23:54:43 +05:30
The GitLab Runner GraphQL API endpoints will not return `paused` or `active` as a status in GitLab 16.0.
In a future v5 of the REST API, the endpoints for GitLab Runner will also not return `paused` or `active`.
2021-12-11 22:18:48 +05:30
2022-01-26 12:08:38 +05:30
A runner's status will only relate to runner contact status, such as:
`online`, `offline`, or `not_connected`. Status `paused` or `active` will no longer appear.
2021-12-11 22:18:48 +05:30
When checking if a runner is `paused`, API users are advised to check the boolean attribute
2022-04-04 11:22:00 +05:30
`paused` to be `true` instead. When checking if a runner is `active`, check if `paused` is `false`.
2021-12-11 22:18:48 +05:30
stage: Verify
tiers: [Core, Premium, Ultimate]
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/344648
documentation_url: https://docs.gitlab.com/ee/api/runners.html