[Misc] Added Workzone service to helm chart

[anirudhprasad-sap]

Add SAP Build Work Zone Standard Edition(local-entry-point plan) Support to Helm Chart

New Feature

✨ Adds support for SAP Build Work Zone, Standard Edition (build-workzone-standard) 'local-entry-point' plan to the CAP Operator Helm chart plugin (v0.20.0). When enabled, the plugin generates a build-workzone-standard service instance (local-entry-point plan) and its binding, and updates the relevant workloads accordingly.

Changes

• files/workzone.yaml.hbs: New Mustache template defining the build-workzone-standard service instance and binding, with providerId (truncated to 20 chars) and exposureId parameters derived from the app name.
• files/approuter.yaml.hbs: Added conditional inclusion of the workzone binding in consumedBTPServices and injects the OWN_SAP_CLOUD_SERVICE environment variable when Workzone Standard is enabled.
• files/workloads.yaml.hbs: Added conditional inclusion of the workzone binding in the contentDeploy job's consumedBTPServices when Workzone Standard is enabled.
• lib/add.js: Extracted hasWorkzoneStandard from the project descriptor; computes workzoneProviderId (app name, max 20 chars) and conditionally merges workzone.yaml.hbs into values.yaml during the combine step.
• test/add.test.js: Added integration test verifying correct generation of the Workzone service instance, binding, approuter OWN_SAP_CLOUD_SERVICE env var, and content deploy binding when workzone-standard is added.
• CHANGELOG.md: Added entry for version 0.20.0 documenting the new Workzone Standard support.
• package.json / package-lock.json: Bumped version from 0.19.0 to 0.20.0.

• 🔄 Regenerate and Update Summary

PR Bot Information

Version: 1.29.26

• Event Trigger: pull_request.edited
• LLM: anthropic--claude-4.6-sonnet
• Output Template: Default Template
• File Content Strategy: Full file content
• Summary Prompt: Default Prompt
• Correlation ID: 10bb64f0-96f0-11f1-9b9b-f6f21fe50925

[hyperspace-pr-bot]

The PR introduces workzone-standard support but has several correctness issues: {{strippedAppName}} is an undefined Mustache variable that will render literally instead of being substituted, hasWorkzoneStandard appears to never be populated by readProject() meaning the feature will silently be skipped, and the new test case mutates the shared bookshop fixture without cleanup, risking interference with subsequent tests that compare against fixed YAML snapshots.

PR Bot Information

Version: 1.29.26

• File Content Strategy: Full file content
• Event Trigger: pull_request.opened
• LLM: anthropic--claude-4.6-sonnet
• Correlation ID: 07db3be0-9659-11f1-883c-3db67b910bc0

[hyperspace-pr-bot]

Summary

The following content is AI-generated and provides a summary of the pull request:

---

Add SAP Build Work Zone Standard Edition Support to Helm Chart (v0.20.0)

New Feature

✨ Adds support for SAP Build Work Zone, Standard Edition (workzone-standard) to the CAP Operator Helm chart plugin. When enabled, the plugin generates a build-workzone-standard service instance using the local-entry-point plan, along with its binding, and updates the relevant workloads accordingly.

Changes

• files/workzone.yaml.hbs: New Mustache template defining the build-workzone-standard service instance and binding, with providerId (truncated to 20 chars) and exposureId parameters derived from the app name.
• files/approuter.yaml.hbs: Added conditional inclusion of the workzone binding in consumedBTPServices and injects the OWN_SAP_CLOUD_SERVICE environment variable when Workzone Standard is enabled.
• files/workloads.yaml.hbs: Added conditional inclusion of the workzone binding in the contentDeploy job's consumedBTPServices when Workzone Standard is enabled.
• lib/add.js: Extracts hasWorkzoneStandard from the project descriptor, computes workzoneProviderId (app name, max 20 chars), and conditionally merges workzone.yaml.hbs into values.yaml during the combine step.
• test/add.test.js: Added integration test verifying correct generation of the Workzone service instance, binding, approuter OWN_SAP_CLOUD_SERVICE env var, and content deploy binding when workzone-standard is added.
• CHANGELOG.md: Added entry for version 0.20.0 documenting the new Workzone Standard support.
• package.json / package-lock.json: Bumped version from 0.19.0 to 0.20.0.

---

• 🔄 Regenerate and Update Summary
• ✏️ Insert as PR Description (deletes this comment)
• 🗑️ Delete comment

PR Bot Information

Version: 1.29.26

• Event Trigger: pull_request.ready_for_review
• Summary Prompt: Default Prompt
• Correlation ID: b36b6080-9707-11f1-9bf2-503d2084edf3
• File Content Strategy: Full file content
• LLM: anthropic--claude-4.6-sonnet
• Output Template: Default Template

[hyperspace-pr-bot]

The PR has multiple substantive bugs already flagged by prior reviewers (undefined {{strippedAppName}} in both templates, hasWorkzoneStandard never being set by readProject(), and test isolation pollution from the shared bookshop directory). The one new issue I found and commented on is a duplicate redundant assignment of project.workzoneProviderId outside its guard, which should be removed to avoid confusion. The author should address all open comments before merging.

PR Bot Information

Version: 1.29.26

• Event Trigger: pull_request.ready_for_review
• File Content Strategy: Full file content
• LLM: anthropic--claude-4.6-sonnet
• Correlation ID: b36b6080-9707-11f1-9bf2-503d2084edf3

[Pavan-SAP]

Looks good.. ✅

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
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