Include project path in agent info API response
What does this MR do and why?
Adds the project path to the list of fields returned by the /kubernetes/agent_info
internal API endpoint.
The path will be used by KAS to default to the agent project if no GitOps manifest project is specified, which will simplify configurations that keep manifests in the same project as the agent:
Before:
gitops:
manifest_projects:
- id: gitlab-org/cluster-integration/gitlab-agent
paths:
- glob: '/team1/app1/*.yaml'
After (missing id
means the agent's project is used):
gitops:
manifest_projects:
- paths:
- glob: '/team1/app1/*.yaml'
Note that this change alone will have no impact on behaviour, a corresponding change will need to be made in the agent project.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #346585 (closed)