ai:chore: Implement direct types for: CloudNumberRegistryCustomRange#9634
ai:chore: Implement direct types for: CloudNumberRegistryCustomRange#9634factorybot-robot wants to merge 1 commit into
Conversation
|
🤖 AI Factory started investigating CI check failures for this pull request. |
2 similar comments
|
🤖 AI Factory started investigating CI check failures for this pull request. |
|
🤖 AI Factory started investigating CI check failures for this pull request. |
|
🤖 AI Factory has attempted to fix CI failures for this PR 3 times since the last commit and is giving up. Human assistance is required. |
310a7c5 to
aaa85ba
Compare
Investigating validate-generated-files failureRun: 27244997482
Investigating validations failureRun: 27244997463 (This report was generated by overseer) |
|
🤖 AI Factory started addressing review feedback for this pull request. |
2 similar comments
|
🤖 AI Factory started addressing review feedback for this pull request. |
|
🤖 AI Factory started addressing review feedback for this pull request. |
aaa85ba to
04daec0
Compare
|
I have resolved the validations check failure by regenerating the Resource Go clients. Specifically:
(This comment was generated by overseer) |
|
🤖 AI Factory started addressing review feedback for this pull request. |
04daec0 to
37f6014
Compare
|
I have successfully rebased this Pull Request on the latest master branch. All validation checks and unit tests have been verified locally (including code formatting, vetting, and ensuring generated files are perfectly up to date). The clean rebased commit has been force-pushed to trigger a fresh CI run. (This comment was generated by overseer) |
|
🤖 AI Factory started addressing review feedback for this pull request. |
|
I have verified that all CI check failures and local validations (including (This comment was generated by overseer) |
|
🤖 AI Factory started addressing review feedback for this pull request. |
|
I have verified that all CI checks, local validations (including All code formatting is perfect and no compilation or linter issues remain. The PR is fully ready for final review and approval. /assign @barney-s (This comment was generated by overseer) |
|
🤖 AI Factory started addressing review feedback for this pull request. |
|
I have completed a thorough check of the PR status:
The pull request is fully validated, clean, and ready for review and approval. /assign @barney-s (This comment was generated by overseer) |
|
🤖 AI Factory started addressing review feedback for this pull request. |
|
I have verified the status of this Pull Request and confirmed that all local checks and validation tests are passing successfully:
All CI checks and local validations have succeeded. The PR is fully validated, green, and ready for final review and approval. /assign @barney-s (This comment was generated by overseer) |
|
🤖 AI Factory started addressing review feedback for this pull request. |
This commit implements the initial v1alpha1 KRM types, CRD, and IdentityV2 for CloudNumberRegistryCustomRange using the "direct" controller approach.
- Scaffolding Types: Configured a service-specific ".pb" compile loop in "generate.sh" to support the extremely recent "google.cloud.numberregistry" APIs without modifying the global pin. Scaffolding Go types under "apis/cloudnumberregistry/v1alpha1".
- Identity & References: Implemented "CloudNumberRegistryCustomRangeIdentity" supporting "projects/{project}/locations/{location}/customRanges/{customrange}" template with validation and parsing. Implemented "CloudNumberRegistryCustomRangeRef" for referencing.
- Manifests and RBAC: Generated CRD manifest and appended appropriate RBAC permissions to "cnrm_admin" and "cnrm_viewer" cluster roles.
- Testing: Added comprehensive unit tests in "cloudnumberregistrycustomrange_identity_test.go" confirming parsing and external reference validation.
- Journaling: Recorded findings and technical implementation details under ".gemini/journals/cloudnumberregistry.md".
Fix: 9633
37f6014 to
20995ce
Compare
|
I have successfully rebased this Pull Request on the latest master branch. All unit tests, file validations, and linters have been verified to pass cleanly locally. Pushed the updated branch to trigger a fresh CI run. (This comment was generated by overseer) |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
🤖 AI Factory started addressing review feedback for this pull request. |
|
I have run all the local presubmits and validations on this cleanly rebased branch:
The branch is fully ready for review and approval! (This comment was generated by overseer) |
This PR implements the initial v1alpha1 KRM types, CRD, and IdentityV2 for the
CloudNumberRegistryCustomRangeresource using the "direct" approach.Implementation Details:
generate.shto compilegoogle.cloud.numberregistry.v1alphafrom Google APIs at target commitfe9f668e59b5448d27564d2b89b5aed97b74f8d7without changing the globalapis/git.versionspin. This prevents generating hundreds of unrelated changes across other direct resources. Scaffolding and types are added underapis/cloudnumberregistry/v1alpha1.CloudNumberRegistryCustomRangeIdentitymapping the canonicalprojects/{project}/locations/{location}/customRanges/{customrange}template. ImplementedCloudNumberRegistryCustomRangeRefsupport for dependency references.CloudNumberRegistryCustomRangeand registered RBAC rules incnrm_adminandcnrm_viewer.cloudnumberregistrycustomrange_identity_test.go. Passed local validation checks successfully via./scripts/validate-prereqs.sh..pbcompilation solution in.gemini/journals/cloudnumberregistry.md.Chore file: .agents/greenfield-direct-new-resource-types.md
Fixes #9633
This Pull Request was generated by the overseer agent (powered by the gemini-3.5-flash model).