Update vertex.mdx#763
Conversation
Greptile SummaryThis PR updates the Vertex AI provider documentation prerequisite. The main changes are:
Confidence Score: 4/5This is close, but the role name should be corrected before merging.
docs/llm-providers/vertex.mdx Important Files Changed
Prompt To Fix All With AIFix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 1
docs/llm-providers/vertex.mdx:53
**Use Vertex role name** The role ID `roles/aiplatform.user` is correct, but the display name shown here can send users to the wrong IAM search term. In the Vertex AI setup flow, users searching by role name need `Vertex AI User`; searching for `Agent Platform User` can return no matching role even though the ID points to the right permission set.
```suggestion
2. Ensure your account has the `Vertex AI User` role (`roles/aiplatform.user`)
```
Reviews (2): Last reviewed commit: "Update vertex.mdx" | Re-trigger Greptile |
|
|
||
| 1. Enable the Vertex AI API in your Google Cloud project | ||
| 2. Ensure your account has the `Vertex AI User` role | ||
| 2. Ensure your account has the `Agent Platform User` role (`roles/aiplatform.user`) |
There was a problem hiding this comment.
This page is for the Vertex AI provider, but the prerequisite now leads with Agent Platform User. A user searching IAM by that display name during Vertex AI setup may miss the expected Vertex AI User role and choose a broader role instead, even though the role ID is correct.
| 2. Ensure your account has the `Agent Platform User` role (`roles/aiplatform.user`) | |
| 2. Ensure your account has the `Vertex AI User` role (`roles/aiplatform.user`) |
Prompt To Fix With AI
This is a comment left during a code review.
Path: docs/llm-providers/vertex.mdx
Line: 53
Comment:
**Vertex Role Name Mismatch**
This page is for the Vertex AI provider, but the prerequisite now leads with `Agent Platform User`. A user searching IAM by that display name during Vertex AI setup may miss the expected `Vertex AI User` role and choose a broader role instead, even though the role ID is correct.
```suggestion
2. Ensure your account has the `Vertex AI User` role (`roles/aiplatform.user`)
```
How can I resolve this? If you propose a fix, please make it concise.|
|
||
| 1. Enable the Vertex AI API in your Google Cloud project | ||
| 2. Ensure your account has the `Vertex AI User` role | ||
| 2. Ensure your account has the `Agent Platform User` role (`roles/aiplatform.user`) |
There was a problem hiding this comment.
Use Vertex role name The role ID
roles/aiplatform.user is correct, but the display name shown here can send users to the wrong IAM search term. In the Vertex AI setup flow, users searching by role name need Vertex AI User; searching for Agent Platform User can return no matching role even though the ID points to the right permission set.
| 2. Ensure your account has the `Agent Platform User` role (`roles/aiplatform.user`) | |
| 2. Ensure your account has the `Vertex AI User` role (`roles/aiplatform.user`) |
Prompt To Fix With AI
This is a comment left during a code review.
Path: docs/llm-providers/vertex.mdx
Line: 53
Comment:
**Use Vertex role name** The role ID `roles/aiplatform.user` is correct, but the display name shown here can send users to the wrong IAM search term. In the Vertex AI setup flow, users searching by role name need `Vertex AI User`; searching for `Agent Platform User` can return no matching role even though the ID points to the right permission set.
```suggestion
2. Ensure your account has the `Vertex AI User` role (`roles/aiplatform.user`)
```
How can I resolve this? If you propose a fix, please make it concise.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
No description provided.