-
Notifications
You must be signed in to change notification settings - Fork 837
OCPSTRAT-3624: Add Licenses field to GCPDisk struct #2980
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
redhat-chai-bot
wants to merge
1
commit into
openshift:master
Choose a base branch
from
redhat-chai-bot:mapi-gcp-disk-licenses
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: openshift/api
Length of output: 50370
🏁 Script executed:
Repository: openshift/api
Length of output: 50370
🏁 Script executed:
Repository: openshift/api
Length of output: 1581
🏁 Script executed:
Repository: openshift/api
Length of output: 1568
🏁 Script executed:
Repository: openshift/api
Length of output: 4481
🌐 Web query:
Google Compute Engine API Disk resourcelicensesfield accepted URI format and license resource URL format💡 Result:
In the Google Compute Engine API, the licenses field in a Disk resource accepts a list of string values, where each string is the full URI of a License resource [1][2][3]. License Resource URI Format The standard URI format for a license resource is: https://www.googleapis.com/compute/v1/projects/{project}/global/licenses/{license_name} [2][4][5] In this structure: - {project}: The name of the project that owns the license (e.g., rhel-cloud, windows-cloud, suse-cloud) [2][4][5]. - {license_name}: The specific name of the license (e.g., rhel-9-server, windows-server-2022-dc) [2][4][5]. Usage in API Requests When updating or specifying licenses via the Compute Engine API (e.g., in a disks.update or disks.insert request), you provide the full URI string [2][6][5]. Example JSON body for a PATCH request: { "name": "DISK_NAME", "licenses": [ "https://www.googleapis.com/compute/v1/projects/rhel-cloud/global/licenses/rhel-9-server" ] } [2][6][5] Note that while the API documentation sometimes refers to license "references" by their path suffix (e.g., projects/rhel-cloud/global/licenses/rhel-9-server) in descriptive text [2], the accepted format for the field in API request payloads is the fully qualified HTTPS URI [2][6][5]. Additionally, do not confuse the licenses field with the licenseCodes field, which accepts integer license codes instead of URI strings [1][7][4].
Citations:
🏁 Script executed:
Repository: openshift/api
Length of output: 3996
🏁 Script executed:
Repository: openshift/api
Length of output: 25705
🏁 Script executed:
Repository: openshift/api
Length of output: 50369
Enforce the documented GCP license URL contract.
The existing markers enforce only list size and item length. Add an anchored
+kubebuilder:validation:items:Patternallow-list for full GCP License resource URIs, and add invalid-value tests.🤖 Prompt for AI Agents
Sources: Path instructions, MCP tools