Skip to content

Comments

[Misc] Plugin: providerSubaccountId runtime support added#85

Open
Pavan-SAP wants to merge 1 commit intomainfrom
provider-appId
Open

[Misc] Plugin: providerSubaccountId runtime support added#85
Pavan-SAP wants to merge 1 commit intomainfrom
provider-appId

Conversation

@Pavan-SAP
Copy link
Contributor

@Pavan-SAP Pavan-SAP commented Feb 20, 2026

Add providerSubaccountId Runtime Support to CAP Operator Plugin

New Features

✨ Added support for the providerSubaccountId field across the CAP Operator plugin to prepare for its transition to a mandatory field in upcoming releases.

Changes

This pull request introduces the providerSubaccountId parameter throughout the CAP Operator plugin infrastructure, ensuring it is properly handled in runtime value generation, schema validation, and template files.

  • bin/cap-op-plugin.js: Added providerSubaccountId to required fields for both service-only and full application charts, and included a new interactive prompt to capture the provider sub-account ID during runtime value generation.

  • files/chart/values.yaml.hbs & files/configurableTemplatesChart/values.yaml.hbs: Added providerSubaccountId field with documentation comment to the BTP configuration section, changing globalAccountId from mandatory (with inline comment) to optional.

  • files/chart/values.schema.json & files/configurableTemplatesChart/values.schema.json: Removed globalAccountId from the required fields array in the BTP schema definition and added providerSubaccountId as an optional string property.

  • files/runtime-values.yaml.hbs: Added providerSubaccountId interpolation to the BTP section of the runtime values template.

  • lib/util.js: Modified the CAP Operator Custom Resource template generation to include providerSubaccountId in the spec section alongside globalAccountId.

  • test/cap-op-plugin.test.js: Updated all test cases to include the new providerSubaccountId prompt response, adjusting the call sequence indices for subsequent prompts across multiple chart type scenarios (standard, configurable templates, service-only, and IAS variants).

  • Test fixture files (test/files/expectedChart/*.yaml, test/files/expectedConfigurableTemplatesChart/*.yaml, test/files/*.yaml): Updated all expected output files and test input files to include the providerSubaccountId field in the BTP configuration section, ensuring consistency across all test scenarios.

  • 🔄 Regenerate and Update Summary

📬 Subscribe to the Hyperspace PR Bot DL to get the latest announcements and pilot features!

PR Bot Information

Version: 1.17.61 | 📖 Documentation | 🚨 Create Incident | 💬 Feedback

  • Event Trigger: pull_request.edited
  • Summary Prompt: Default Prompt
  • LLM: anthropic--claude-4.5-sonnet
  • Correlation ID: 51c39610-1159-11f1-8b02-59114c28cfe0
  • Output Template: Default Template

hyperspace-insights[bot]

This comment was marked as outdated.

@Pavan-SAP Pavan-SAP marked this pull request as draft February 23, 2026 10:00
Enhancement to source `providerSubaccountId` at runtime.
- misc adjustments until the field becomes mandatory (soon).
@sonarqubecloud
Copy link

@Pavan-SAP Pavan-SAP marked this pull request as ready for review February 24, 2026 08:17
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