Remove all-in-one distribution mgt-portal -> platform-api healthcheck temporarily

[malinthaprasan]

Purpose

There is a failing heathcheck and it causes the distribution startup to fail. Disabling it temporarilty until a proper solution is added.

Tracked via - #658

Goals

Describe what solutions this feature or fix introduces to address the problems outlined above.

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI. Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Automation tests

• Unit tests

  Code coverage information

• Integration tests

  Details about the test cases and coverage

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
• Ran FindSecurityBugs plugin and verified report? yes/no
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Summary by CodeRabbit

• Chores
  • Updated service startup configuration to adjust initialization sequencing in the deployment stack.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Removed the health check dependency on platform-api from the management-portal service in the Docker Compose configuration. The management-portal service will no longer wait for platform-api to be healthy before starting, altering the service startup sequence.

Changes

Cohort / File(s)	Summary
Docker Compose Configuration distribution/all-in-one/docker-compose.yaml	Removed depends_on block with condition: service_healthy for platform-api under management-portal service, changing startup ordering

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 A hoppy hop, a line removed so quick,
No waiting now—the startup's got no trick!
Platform-api and portal run their race,
With independence, they both find their place!
Dependencies fade like morning dew,
Services spring forth, bold and new! 🚀

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is incomplete. While the Purpose section is filled with a clear explanation of the issue, most required template sections (Goals, Approach, User stories, Documentation, Automation tests, Security checks, Samples, Related PRs, Test environment) contain only placeholder text with no actual content.	Complete the missing sections: Goals section should explain what disabling the healthcheck achieves; Approach should detail the specific change; Documentation should indicate if doc updates are needed; Automation tests and Security checks should be explicitly addressed; Test environment should list tested configurations.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: removing a healthcheck dependency in the docker-compose configuration.
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 docstrings

---

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.}