feat(resources): implement GcpStorageResource and GcpCloudSqlResource types #5445

Open
opened 2026-04-09 06:51:40 +00:00 by HAL9000 · 1 comment
Owner

Background

Part of Epic #5176 (Extended Resource Types — Cloud Infrastructure, Database & Virtual Resources). Adds GCP cloud infrastructure resource types for Google Cloud Storage buckets and Cloud SQL instances.

Expected Behavior

  • GcpStorageResource type for GCS bucket resources with bucket name, project, and region fields
  • GcpCloudSqlResource type for Cloud SQL instances with instance name, database, and connection string fields
  • Both types use physical: bool = True per spec
  • Resource handlers for GCP types support CRUD operations

Subtasks

  • Implement GcpStorageResource model with GCS-specific fields (bucket_name, project_id, region)
  • Implement GcpCloudSqlResource model with Cloud SQL fields (instance_name, database_name, connection_string)
  • Register both types in the resource type registry
  • Implement resource handlers for GCP resource types
  • Write Behave unit tests for GCP resource types

Definition of Done

  • GcpStorageResource and GcpCloudSqlResource types functional
  • Both types registered in resource type registry
  • Resource handlers support CRUD operations
  • All nox stages pass
  • Coverage >= 97%

Metadata

  • Branch: feat/v3.6.0/extended-resource-types
  • Commit Message: feat(resources): implement GcpStorageResource and GcpCloudSqlResource types
  • Milestone: v3.6.0
  • Parent Epic: #5176

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planner

## Background Part of Epic #5176 (Extended Resource Types — Cloud Infrastructure, Database & Virtual Resources). Adds GCP cloud infrastructure resource types for Google Cloud Storage buckets and Cloud SQL instances. ## Expected Behavior - `GcpStorageResource` type for GCS bucket resources with bucket name, project, and region fields - `GcpCloudSqlResource` type for Cloud SQL instances with instance name, database, and connection string fields - Both types use `physical: bool = True` per spec - Resource handlers for GCP types support CRUD operations ## Subtasks - [ ] Implement `GcpStorageResource` model with GCS-specific fields (bucket_name, project_id, region) - [ ] Implement `GcpCloudSqlResource` model with Cloud SQL fields (instance_name, database_name, connection_string) - [ ] Register both types in the resource type registry - [ ] Implement resource handlers for GCP resource types - [ ] Write Behave unit tests for GCP resource types ## Definition of Done - [ ] `GcpStorageResource` and `GcpCloudSqlResource` types functional - [ ] Both types registered in resource type registry - [ ] Resource handlers support CRUD operations - [ ] All nox stages pass - [ ] Coverage >= 97% ## Metadata - **Branch**: `feat/v3.6.0/extended-resource-types` - **Commit Message**: `feat(resources): implement GcpStorageResource and GcpCloudSqlResource types` - **Milestone**: v3.6.0 - **Parent Epic**: #5176 --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
HAL9000 added this to the v3.6.0 milestone 2026-04-09 06:54:15 +00:00
Author
Owner

Label compliance fix applied:

  • Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#5445
No description provided.