Update tags in various runbooks to include 'data:config' and 'data:logs-regexp' for enhanced categorization and clarity in resource management tasks.

[stewartshea]

All data tags have been added across all codebundles. Here's a summary of what was done:

Summary

422 data tags were added across 106 robot files in all codebundles:

Tag	Count	Description
data:config	341	Configuration data (health checks, describe outputs, metrics, status, etc.)
data:logs-regexp	47	Filtered logs (error patterns, diagnostic logs, log analytics, etc.)
data:logs-bulk	28	General/unfiltered logs (activity logs, raw log tailing, invocation logs)
data:logs-stacktrace	6	Stacktrace-specific log data

Tag Assignment Logic

• data:config - Tasks that collect configuration state, resource health status, metrics, describe output, cluster/service configurations, security settings, cost analysis, etc.
• data:logs-regexp - Tasks that fetch logs with filtering (error patterns, severity filters, diagnostic analysis, grep-based inspection)
• data:logs-bulk - Tasks that fetch general logs with minimal filtering (tail logs, activity logs, raw log dumps, invocation logs)
• data:logs-stacktrace - Tasks specifically targeting stacktrace/traceback extraction from logs

Excluded from tagging

• Operational/chaos tasks (chaos-flux, chaos-namespace, chaos-workload, webapp-ops, postgres-operations) - these modify state rather than collecting data
• Health score generation tasks ("Generate Health Score", "Generate Namespace Score") - these aggregate existing data into scores
• Pure scoring SLI tasks in gh-actions-health/sli.robot - these calculate scores without adding raw data

---

Note

Medium Risk
Mostly metadata/tagging changes, but the GMP endpoint change alters which GCP project is queried and could break checks if ${GCP_PROJECT_ID} is unset or incorrect.

Overview
Standardizes task categorization across many runbook.robot/sli.robot files by adding data:config, data:logs-regexp, and data:logs-bulk tags (and similar) to existing tasks for configuration/metrics collection vs log collection.

Also fixes curl-gmp-kong-ingress-inspection to query GMP using ${GCP_PROJECT_ID} instead of a hardcoded project, and updates an azure-storage-cost-optimization README example table accordingly.

^{Written by Cursor Bugbot for commit b5b8224. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Operational sync task incorrectly tagged as data collection

Low Severity

The Sync Container Images into Azure Container Registry task is tagged with data:config, but it's an operational task that modifies state by synchronizing/pushing container images into ACR. The PR's own tagging rules state that operational tasks which modify state (rather than collecting data) are excluded from data tagging. This task's documentation explicitly says it "Synchronizes the latest container images into an ACR repository," which is a write operation, not a data collection task.