Preconfigure GitLab workflow extension when a new workspace is created
MR - Update Tools Injector Image, PAT scope with add... (!156714 - merged)
Description
GitLab Workflow extension requires a PAT with api
scope. We already create a new PAT per workspace with write_repository
scope. We should extend this and pre-configure the GitLab Workflow extension as per the config defined in [VS Code] Read gitlab token from a file to conf... (gitlab-vscode-extension#1250 - closed)
Acceptance Criteria
-
The tools-injector image is updated to the latest image published from Add GitLab VS Code extension to the tools-injec... (#463502 - closed) -
The environment variables required for GitLab VS Code extension to work inside the workspace are injected. -
The PAT injected inside the workspace needs to have additional api
access for the Gitlab VS Code extension to work. -
When workspace is created, Duo Chat and Code Suggestions work out of the box.
Technical Requirements
TODO: Fill out or delete [If applicable, please list out any technical requirements for this feature/enhancement.]
Design Requirements
TODO: Fill out or delete [If applicable, please provide a link to the design specifications for this feature/enhancement.]
Impact Assessment
TODO: Fill out or delete [Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.]
User Story
TODO: Fill out or delete [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.]