Add Orion regression-detection config for cost metrics rollup

[pragya811]

Type of change

Note: Fill x in []

• bug
• enhancement
• documentation
• dependencies

Description

Mirrors cg-policy-regressions.yaml but targets
cloud-governance-orion-cost-metrics-index (produced by orion_cost_metrics_rollup.py): total/aws/azure/ibm_cost, Increase+Decrease each. gcp_cost is intentionally omitted for now since a stale feed would only generate noise; can be added back once that feed reports fresh data.

For security reasons, all pull requests need to be approved first before running any automated CI

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 3ffc9589-1d74-4111-ad6f-fda9e595517a

📥 Commits

Reviewing files that changed from the base of the PR and between 441b66c and 5fea3ad.

📒 Files selected for processing (1)

• orion-configs/cg-cost-regressions.yaml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

📝 Summary

Summary by CodeRabbit

• New Features
  • Added regression monitoring for total, AWS, Azure, and IBM cost metrics by synthetic cost-center account.
  • Configured alerts for cost increases or decreases exceeding 20%.

Walkthrough

The PR adds an Orion configuration for cost regression detection. It scopes checks to synthetic cost-center accounts and adds bidirectional threshold checks for total, AWS, Azure, and IBM costs. GCP checks remain omitted because its feed is stale.

Changes

Cost Regression Detection

Layer / File(s)	Summary
Test metadata and account scope orion-configs/cg-cost-regressions.yaml	Defines the Orion test metadata, invocation documentation, and synthetic cost-center account scope.
Bidirectional cost checks orion-configs/cg-cost-regressions.yaml	Adds increase and decrease checks with a threshold of 20 for total, AWS, Azure, and IBM costs. GCP checks are omitted.
Estimated code review effort: 2 (Simple)	~10 minutes

Merge Risk: ⚪ Minimal · up to 5fea3

This adds scoped bidirectional cost-regression checks for supported cloud feeds while intentionally excluding stale GCP data. The configuration is ready to merge.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the addition of an Orion regression-detection configuration for cost metrics rollup.
Description check	✅ Passed	The description accurately explains the configuration scope, covered cost metrics, increase and decrease checks, and intentional omission of stale GCP data.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

---

_{Comment @coderabbitai help to get the list of available commands.}

[ebattat]

/approve