Skip to content

Add gcp-artifact-registry-spend-analysis CodeBundle#700

Open
rw-codebundle-agent[bot] wants to merge 1 commit into
mainfrom
codebundle/gcp-artifact-registry-spend-analysis-issue-133
Open

Add gcp-artifact-registry-spend-analysis CodeBundle#700
rw-codebundle-agent[bot] wants to merge 1 commit into
mainfrom
codebundle/gcp-artifact-registry-spend-analysis-issue-133

Conversation

@rw-codebundle-agent

Copy link
Copy Markdown
Contributor

Summary

  • Adds gcp-artifact-registry-spend-analysis CodeBundle for issue automatic-index-update #133 (parent automatic-index-update #132)
  • Queries BigQuery billing export for Artifact Registry and legacy GCR SKUs with spend breakdown, top contributors, MoM comparison, anomaly detection, and optimization recommendations
  • Includes in-repo sli.robot scoring anomaly signals, MoM growth, and project spend concentration (0–1 health score)

Design spec alignment

  • Implements all five tasks from the design spec with configurable thresholds via env vars
  • Reuses billing export query patterns from gcp-project-cost-health
  • Uses project resource type (collection convention; spec listed gcp_projects)
  • BigQuery billing export does not expose repository names; recommendations cross-reference gcp-artifact-registry-governance

Scoring

  • Self-check: 104/104 (python -m scorer.score codebundles/gcp-artifact-registry-spend-analysis)

Test plan

  • Static structure validation: cd codebundles/gcp-artifact-registry-spend-analysis/.test && task
  • Run runbook against a workspace with BigQuery billing export access
  • Verify SLI health score drops when MoM growth or project concentration thresholds are breached
  • Confirm legacy GCR SKU detection in report-top-artifact-cost-contributors.sh

Made with Cursor

Analyze Artifact Registry and legacy GCR spend from BigQuery billing export with MoM trends, anomaly detection, and optimization recommendations for issue #133.

Co-authored-by: Cursor <cursoragent@cursor.com>
@rw-codebundle-agent rw-codebundle-agent Bot requested a review from a team as a code owner June 30, 2026 18:38
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.

0 participants