Expose cluster agents API link as field in project REST API

Hi @msedlakjakubowski, please review this documentation Merge Request.

Thank you for your contribution to GitLab. We believe that everyone can contribute and contributions like yours are what make GitLab great!

Our Merge Request Coaches will ensure your contribution is reviewed in a timely manner*.
If you haven't, please set up a DANGER_GITLAB_API_TOKEN.
You can comment @gitlab-bot label ~"group::" to add a group label.
If you need help moving the MR forward or finding a reviewer, feel free to ask @gitlab-bot help or ping a Merge Request Coach.
Read more on how to get help.
You can provide feedback on the GitLab Contributor Experience in this survey

This message was generated automatically. You're welcome to improve it.

added Community contribution label

assigned to @tuxtimo

mentioned in commit tuxtimo/gitlab@90adba98

added 1 commit

90adba98 - Expose `agent_ids` field in project REST API

Compare with previous version

@gitlab-bot request_review

Hey there @kushalpandya, can you please take a look at this MR and help @tuxtimo out?

@tuxtimo,

Thanks for requesting a review. I've notified the merge request coaches.

They will get back to you as soon as they can.

If you have not received any response, you may ask for a review again after 1 day.

mentioned in commit tuxtimo/gitlab@d31457ed

added 1 commit

d31457ed - Expose `agent_ids` field in project REST API

Compare with previous version

mentioned in commit tuxtimo/gitlab@6751b2e8

added 1 commit

6751b2e8 - Expose `agent_ids` field in project REST API

Compare with previous version

mentioned in issue gitlab-org/quality/triage-reports#6986 (closed)

changed milestone to %Backlog

added GitLab Core GitLab Free [deprecated] Accepting merge requests [deprecated] good for new contributors auto updated devopsconfigure [DEPRECATED] groupconfigure [DEPRECATED] sectionops typefeature workflowready for development labels

@kerrizor thanks for checking this out :) However, I've noticed that the labels look more like the ones usually assigned to issues and not "ready-to-review" MRs. Any chance something got mixed up?

requested review from @msedlakjakubowski

changed milestone to %14.10

added workflowin review label and removed workflowready for development label

removed auto updated label

removed [deprecated] Accepting merge requests label

removed [deprecated] good for new contributors label

added Technical Writing docsfeature twdoing labels and removed twtriaged label

added backend twtriaged labels and removed Technical Writing docsfeature twdoing labels

added Technical Writing docsfeature twdoing labels and removed twtriaged label

requested review from @mcelicalderonG

added 1 commit

59525e79 - Link to issue in version note

Compare with previous version

approved this merge request

added twfinished label and removed twdoing label

@msedlakjakubowski, thanks for approving this merge request.

This is the first time the merge request is approved. To ensure full test coverage, please start a new pipeline before merging.

For more info, please refer to the following links:

added 1 commit

1d5f4dfa - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

added 1 commit

832f6baf - Apply 2 suggestion(s) to 1 file(s)

Compare with previous version

mentioned in commit tuxtimo/gitlab@4af417bc

added 1 commit

4af417bc - Expose `agent_ids` field in project REST API

Compare with previous version

mentioned in commit tuxtimo/gitlab@78af6d85

added 1 commit

78af6d85 - Expose `agent_ids` field in project REST API

Compare with previous version

approved this merge request

requested review from @dbalexandre and removed review request for @mcelicalderonG

mentioned in commit tuxtimo/gitlab@b0f29799

added 1 commit

b0f29799 - Expose `agent_ids` field in project REST API

Compare with previous version

removed review request for @dbalexandre

mentioned in issue #355873 (closed)

mentioned in merge request !83270 (merged)

mentioned in commit tuxtimo/gitlab@1720d329

added 1 commit

1720d329 - Expose `_links.cluster_agents` field in project REST API

Compare with previous version

mentioned in commit tuxtimo/gitlab@37d5fc0d

added 1 commit

37d5fc0d - Expose `_links.cluster_agents` field in project REST API

Compare with previous version

changed title from Expose {-agent_ids-} field in project REST API to Expose cluster agents API link as field in project REST API

changed the description

mentioned in issue #357320

removed review request for @msedlakjakubowski

mentioned in commit tuxtimo/gitlab@1be8825f

added 3128 commits

37d5fc0d...9a2c784c - 3127 commits from branch gitlab-org:master
1be8825f - Expose `_links.cluster_agents` field in project REST API

Compare with previous version

changed milestone to %15.0

requested review from @dbalexandre

added 1 commit

3a33a29f - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

resolved all threads

approved this merge request

Suggested Reviewers (beta)

This is an experimental ML-based code reviewer recommendation system created by ~"group::applied ml".

The individuals below may be good candidates to participate in the review based on various factors.

After you review all recommendations, please assign reviewers manually, as this is not done automatically.

You can use slash commands in comments to quickly assign /assign_reviewer @user1.

Reviewers
`@ngaskill`, `@afontaine`, `@rspeicher`, `@stanhu`, `@cablett`

If you do not believe these recommendations are useful or if you do not want to use any of the suggestions, please apply the label Bad Suggested Reviewer. You can also provide feedback for this feature on this issue: https://gitlab.com/gitlab-org/gitlab/-/issues/357923.

Automatically generated by Suggested Reviewers Bot

enabled an automatic merge when the pipeline for 12af6e3c succeeds

@tuxtimo Thanks for your contribution This LGTM I triggered a new pipeline and set MWPS

canceled the automatic merge

enabled an automatic merge when the pipeline for 12af6e3c succeeds

	1 Warning
	1be8825f: The commit body should not contain more than 72 characters per line. For more information, take a look at our Commit message guidelines.

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

If needed, you can retry the danger-review job that generated this comment.

Documentation review

The following files require a review from a technical writer:

doc/api/projects.md

The review does not need to block merging this merge request. See the:

Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
The Technical Writer assigned for that stage and group.
Documentation workflows for information on when to assign a merge request for review.

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
backend	Allen Cook (`@acook.gitlab`) (UTC-4)	Ethan Urie (`@eurie`) (UTC-4)

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

Generated by Danger

merged

@tuxtimo, how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

Leave a or a on this comment to describe your experience.
Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

Have five minutes? Take our survey to give us even more feedback on how GitLab can improve the contributor experience.

Thanks for your help!