[Customer Portal][BE] Remove update level from deployed product

[Rashmika998]

Summary by CodeRabbit

• Refactor
  • Simplified internal data structure by removing an unused field from the backend entity model, reducing payload size and streamlining data processing.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3720fefa-5794-4526-b22e-5ea868a51687

📥 Commits

Reviewing files that changed from the base of the PR and between 2899b3b and 52107a8.

📒 Files selected for processing (1)

• apps/customer-portal/backend/modules/entity/types.bal

💤 Files with no reviewable changes (1)

• apps/customer-portal/backend/modules/entity/types.bal

---

📝 Walkthrough

Walkthrough

The updateLevel field was removed from the DeployedProduct public record in the entity types module. This reduces the record structure by one optional string field, eliminating the corresponding type definition without introducing alternative mechanisms or error handling.

Changes

Cohort / File(s)	Summary
DeployedProduct Type Definition apps/customer-portal/backend/modules/entity/types.bal	Removed the string? updateLevel; field from the DeployedProduct public record.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• [Customer Portal][BE] Customer portal milestone 1 deployed products #194: Directly modifies the same updateLevel field in the DeployedProduct record (adds it back, opposing this removal).
• [Customer Portal][BE] Update deployed products update payload #349: Modifies the same DeployedProduct record, replacing the updateLevel field with an updates/ProductUpdate structure.

Suggested reviewers

• cloby99
• sacheeramesh

Poem

🐰 A field takes flight, so light, so free,
The record grows sleek, lean, spry,
No more strings attached to thee,
Simplicity hops on by! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request has no description provided. The template requires multiple sections including Purpose, Goals, Approach, and others, but all are missing.	Add a comprehensive pull request description following the repository template. Include at least Purpose, Goals, and Approach sections explaining why this field was removed and its impact.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: removing the updateLevel field from the DeployedProduct type in the Customer Portal backend, matching the changeset.
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

📝 Coding Plan

• Generate coding plan for human review comments

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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