[Misc] GlobalAccountId to ProviderSubaccountId migration + Readme update

[anirudhprasad-sap]

Migrate globalAccountId to providerSubaccountId in CAP Operator Helm Charts

New Feature

♻️ Refactor/Migration: Introduced an automatic migration mechanism that detects and replaces the deprecated globalAccountId field with providerSubaccountId in existing CAP Operator Helm chart files when running cds add cap-operator.

Changes

• lib/add.js:

  • Added adoptIncompactibleChanges() method that detects if btp.globalAccountId still exists in chart/values.yaml and automatically migrates it to providerSubaccountId, updates chart/templates/cap-operator-cros.yaml if present, and refreshes values.schema.json from the plugin's bundled templates.
  • Integrated the migration into handleExistingChart() so it runs automatically when re-running cds add cap-operator on an existing chart.
  • Fixed the chart existence check to also verify the chart directory is non-empty before treating it as an existing chart.
  • Minor formatting fix for a multi-line filter condition.

• test/add.test.js:

  • Added three new test cases covering:
    • Migration of globalAccountId → providerSubaccountId in a simple chart.
    • Migration in a configurable template chart (including the CRO template file).
    • Verification that migration is skipped when the chart is already up to date.

• 🔄 Regenerate and Update Summary

PR Bot Information

Version: 1.20.33

• Event Trigger: pull_request.opened
• Correlation ID: 3e2f169e-aad6-4495-a0a9-33f346f62e7d
• Output Template: Default Template
• File Content Strategy: Full file content
• LLM: anthropic--claude-4.6-sonnet
• Summary Prompt: Default Prompt

[hyperspace-insights]

The PR introduces a globalAccountId → providerSubaccountId migration and a guard for empty chart directories, but has several issues worth addressing: a misspelled method name (adoptIncompactibleChanges), a potentially confusing early-exit guard that silently conflates "btp absent" with "globalAccountId absent", a missing warning when the CRO template file doesn't exist but the schema is still overwritten, and a subtle fragility around double-writing values.schema.json during migration. The bare readdirSync('chart') path is also safer when anchored to cds.root.

PR Bot Information

Version: 1.20.33

• LLM: anthropic--claude-4.6-sonnet
• Event Trigger: pull_request.opened
• File Content Strategy: Full file content
• Correlation ID: 3e2f169e-aad6-4495-a0a9-33f346f62e7d

[Pavan-SAP]

✅

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud