fix: Update DRM content ID example to hex format

[Anif7]

• The documentation previously showed the DRM content ID in a hyphenated (non-hex) format.
• The API was updated to return the content ID in hexadecimal format.
• Updated the example in the documentation to match the current API response.

[gemini-code-assist]

Summary of Changes

Hello, 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 aims to enhance the accuracy of the transcoding service documentation by correcting the format of the DRM content ID examples. The change ensures that the documentation aligns with the actual hexadecimal format returned by the API, improving clarity and preventing potential confusion for users.

Highlights

• Documentation Update: The example for drm_content_id in the transcoding service documentation has been updated to reflect the current API response format, which is hexadecimal, rather than the previous hyphenated format.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• docs/transcoding-service/transcode-a-video.md
  • Updated the drm_content_id example format from hyphenated to hexadecimal in both the successful request and webhook response sections.

Activity

• No human activity has been recorded on this pull request yet.

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 updates the example drm_content_id in the transcoding documentation to use a non-hyphenated hexadecimal format. While the change itself is correct and aligns with the API update, it highlights a potential for developer confusion due to inconsistent terminology in related documentation. I have added a comment suggesting a follow-up to improve the clarity and consistency of descriptions for this ID across all relevant documents.

[gemini-code-assist]

The format of drm_content_id is now a non-hyphenated hexadecimal string. This change creates a potential inconsistency with other documentation files (e.g., docs/drm-service/widevine-configuration.md and docs/drm-service/fairplay-configuration.md), which still describe the corresponding content_id as a 'UUID'. While technically a UUID can be represented without hyphens, the term often implies the hyphenated format, which could confuse developers. For better clarity, consider updating the descriptions in those files to be more specific, for example, 'a 32-character hexadecimal string representing the UUID'.