fix(policy): Mention manager field

[c-r33d]

1.) Add an important note, describing that the name field for key managers is no longer used. Users should instead use the manager field.
2.) Pin links directly to a sha to avoid shift

[gemini-code-assist]

Summary of Changes

Hello @c-r33d, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the clarity and reliability of the key manager documentation. It addresses a potential point of confusion by explicitly stating the updated usage of the name and manager fields for key manager identification. Furthermore, it improves the long-term maintainability of the documentation by fixing internal code references to specific commit hashes, preventing future link rot.

Highlights

• Key Manager Field Clarification: Added an important note to the documentation clarifying that the name field for key managers is now considered a friendly name, and the manager field is used for mapping a key to its implementation, effective from Service v0.10.0.
• Documentation Link Stability: Updated all internal code links within the key_managers.md document to pin them directly to specific Git SHAs, ensuring that the links remain valid and point to the correct code versions even if the main branch evolves.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to update the documentation regarding key managers, specifically to note that the manager field should be used instead of the name field for mapping. While the addition of the important note and pinning links to a specific SHA are good steps, the changes introduce significant contradictions within the document. The new note describes the updated behavior, but other sections of the file were not fully updated and still refer to the old logic, which will likely confuse readers. My review focuses on pointing out these inconsistencies and suggesting improvements for clarity.