Skip to content

feat(taskqueue): migrate push queue client to Cloud Tasks v2 while retaining v2beta3 for QueueStats - #412

Open
riddhi-shivhare wants to merge 1 commit into
golang:taskqueue-migration-previewfrom
riddhi-shivhare:migrate-taskqueue-v2-client
Open

riddhi-shivhare wants to merge 1 commit into
golang:taskqueue-migration-previewfrom
riddhi-shivhare:migrate-taskqueue-v2-client

Conversation

@riddhi-shivhare

Copy link
Copy Markdown

Description

Migrate App Engine TaskQueue push queue client operations to GA Cloud Tasks v2 (cloud.google.com/go/cloudtasks/apiv2) across both v1 (taskqueue) and v2 (v2/taskqueue) modules, while retaining v2beta3 exclusively for QueueStats.

Changes

  • Push Queue Client: Switched default Cloud Tasks client instantiation and protobuf types from cloud.google.com/go/cloudtasks/apiv2beta3 to cloud.google.com/go/cloudtasks/apiv2 and apiv2/cloudtaskspb in:
    • taskqueue/cloudtask.go
    • taskqueue/cloudtask_transactional.go
    • v2/taskqueue/cloudtask.go
    • v2/taskqueue/cloudtask_transactional.go
  • QueueStats Retention: Retained apiv2beta3 client and protos strictly for queueStatsInCloudTasks (GetQueue with read_mask for stats), as queue statistics are out of scope for GA.
  • Dual Support: Kept behavior identical across both standard (taskqueue) and modular v2 (v2/taskqueue) packages.

…taining v2beta3 for QueueStats

- Switch Cloud Tasks client and proto packages in task creation, batch creation, task deletion, and transactional staging to apiv2.
- Retain apiv2beta3 exclusively in queueStatsInCloudTasks for QueueStats.
- Apply changes to both v1 (taskqueue/) and v2 (v2/taskqueue/) modules.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant