Skip to content

[Customer Portal][BE] Customer portal milestone 1 deployed products - #194

Merged
Rashmika998 merged 1 commit into
wso2-open-operations:customer-portal-milestone-1from
Rashmika998:customer-portal-milestone-1-deployed-products
Feb 18, 2026
Merged

Rashmika998 merged 1 commit into
wso2-open-operations:customer-portal-milestone-1from
Rashmika998:customer-portal-milestone-1-deployed-products

Conversation

@Rashmika998

@Rashmika998 Rashmika998 commented Feb 18, 2026 •

Copy link
Copy Markdown
Contributor

Description

This PR updates the deployed products response to include additional product-related metadata required for better visibility and management.

Changes

Extended the deployed products response model to include the following fields:

  • version (ReferenceItem?) → Product version
  • cores (int?) → Allocated CPU cores
  • tps (int?) → Allocated TPS
  • releasedOn (string?) → Product release date
  • endOfLifeOn (string?) → Product end-of-life date
  • updateLevel (string?) → Current update level

Updated:

  • Response DTOs/records
  • Mapping logic from entity/service layer
  • Serialization handling

Reason

The existing deployed products response lacked important operational and lifecycle information.

These additional fields enable:

  • Improved product lifecycle tracking
  • Capacity visibility (cores and TPS allocation)
  • Version and update management
  • Frontend dashboards to display richer product insights

Making these fields optional (?) ensures backward compatibility and supports partial data scenarios.

Testing

  • Verified deployed products API returns the new fields
  • Confirmed optional fields behave correctly when data is unavailable

Summary by CodeRabbit

Release Notes

  • New Features
    • Deployed products now display additional metadata including version information, resource allocation details (cores and TPS), and lifecycle tracking (release date, end of life date, and update level).

@Rashmika998 Rashmika998 self-assigned this Feb 18, 2026
@Rashmika998 Rashmika998 added Type/Improvement Marks enhancements or improvements to existing features App/Customer Portal Area/Backend labels Feb 18, 2026
@coderabbitai

coderabbitai Bot commented Feb 18, 2026 •

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉


📝 Walkthrough

Walkthrough

Extended the DeployedProduct record across two type definition files with six new fields (version, cores, tps, releasedOn, endOfLifeOn, updateLevel) to capture product versioning, resource allocations, and lifecycle metadata. Updated the mapDeployedProducts utility function to project these additional fields into the output.

Changes

Cohort / File(s) Summary
Type definitions
apps/customer-portal/backend/modules/entity/types.bal, apps/customer-portal/backend/modules/types/types.bal
Added six new optional fields to public DeployedProduct record: version, cores, tps, releasedOn, endOfLifeOn, and updateLevel to extend product metadata with versioning and lifecycle information.
Utility mapping
apps/customer-portal/backend/utils.bal
Updated mapDeployedProducts function to include new fields (version with id/label projection, cores, tps, releasedOn, endOfLifeOn, updateLevel) in the DeployedProduct output projection.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • cloby99
  • shayanmalinda

Poem

🐰 Six fields hop into view,
Version, cores, and lifecycle too,
Products now richer with detail so new,
Metadata blooms in the morning dew! 🌿

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The PR description covers the key aspects but deviates from the repository template. While it explains the purpose, changes, and testing, it lacks many required sections like Release notes, Documentation, Certification, Marketing, and test coverage details. Consider filling in missing template sections (Release notes, Documentation, Certification, Marketing, test coverage metrics) to align with the repository's PR description standards.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The PR title accurately describes the main change: extending the deployed products response model with additional product metadata for the customer portal backend.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

App/Customer Portal Area/Backend Type/Improvement Marks enhancements or improvements to existing features

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants