Reviewed & tested by the community
Project:
Google Vertex Provider
Version:
2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Issue tags:
Reporter:
Created:
8 Jan 2026 at 08:33 UTC
Updated:
14 May 2026 at 12:50 UTC
Jump to comment: Most recent
Comments
Comment #2
yce commentedComment #4
yce commentedUpdated two minor things, an argument name and the core version requirements.
I don't see any other outstanding compatibility issue.
Comment #5
arianraeesi commentedComment #6
marcus_johansson commentedComment #7
csakiistvanComment #8
csakiistvanEnvironment
Step 1 — Require drupal/ai 2.x and the vertex provider
Update
composer.json:Add the MR patch under
extra.patchesincomposer.json:Then run:
Step 2 — Run database updates
Expected: one pending update for
ai_automators_update_11001runs and completes successfully.Step 3 — Enable the module
Expected output:
Step 4 — Verify the MR changes are present in the installed code
Check the
setAuthentication()method signature:Expected output:
service_accountCheck
core_version_requirement:Expected output:
core_version_requirement: ^10.4 || ^11Step 5 — Create a service account key and configure the provider
Create a GCP service account with Vertex AI permissions and download the JSON key:
Create a Key module entry with the JSON credentials at /admin/config/system/keys/add, then navigate to /admin/config/ai/providers, select Google Vertex, and choose the newly created key from the select field.
Results
core_version_requirement: ^10.4 || ^11present in installed modulesetAuthentication()parameter renamed (original MR:$file_location→$authentication)$service_account— see note)Note on MR !17 patch
The patch from MR !17 cannot be applied because both changes it introduces are already present in the
dev-2.xbranch and have since been extended. The parameter rename went further than the MR proposed:$file_locationwas first renamed to$authentication(MR !17) and subsequently refactored to$service_accountin commit05bb285(refactor: Align GCP credentials naming with industry standards). Thecore_version_requirementchange is also already in place. The MR can be considered resolved; the issue can be closed.The module installs and configures correctly with AI 2.x. Both changes from MR !17 are present in the codebase. Recommending to close this issue as fixed.
This comment was produced with the assistance of an LLM