Skip to content

Conversation

@Zdravko-Genov
Copy link

Description

Made a few improvements:

  • changed the healt.sh - generalized the way the versions are checked
  • added health.ps for win
  • added instruction for use under win

❓ I need some help determine the dependencies and the respective versions.
❗ I noticed there is a dependencies on OpenSSL and Python. They are generally present in Linux, but not on Win.

Checklist - none of those seems applicable ( at this point )

  • I have added relevant error handling and logging messages to help troubleshooting
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation, relevant usage information (if applicable)
  • I have updated the PR title with affected component, related issue number and a short summary of the changes introduced
  • I have added labels for implementation kind (kind/) and version type (version/)
  • I have tested against live environment, if applicable
  • I have synced any structure and/or content vRA-NG improvements with vra-ng and ts-vra-ng archetypes (if applicable)
  • I have my changes rebased and squashed to the minimal number of relevant commits. Notice: don't squash all commits
  • I have added a descriptive commit message with a short title, including a Fixed #XXX - or Closed #XXX - prefix to auto-close the issue

Testing

Locally tested

Release Notes

Related issues and PRs

@Zdravko-Genov Zdravko-Genov requested a review from a team as a code owner November 3, 2025 10:06
@github-actions github-actions bot added the kind/enhancement Enhancement or improvement of existing features label Nov 3, 2025
@Zdravko-Genov Zdravko-Genov force-pushed the improvemnt-of-healt-script branch from a3aec68 to b0135b4 Compare November 3, 2025 10:41
@VenelinBakalov
Copy link
Collaborator

@Zdravko-Genov thank you for your contribution! I will try to do a more in-depth check soon, for now I will just leave small comments regarding the dependencies I saw

@{ name = "Node.js"; cmd="node --version"; min="12.0"; max="24.0" },
@{ name = "Python"; cmd="python --version"; min="3.2"; max="3.14" },
@{ name = "Pip"; cmd="pip --version"; min="25.0"; max="26.0" },
@{ name = "OpenSSL"; cmd="openssl version"; min="10.0"; max="17.0" }
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think openssl shouldn't be required. If you encountered it in the instructions for generating an certificates for signing the Orchestrator packages this is meant to be just an example on how you can generate it. The prereq is having that certificate for signing packages and is only for Orchestrator projects but they can be generated in other ways including from external system and may also not be present on the system that is building the project but can be located in an artifactory.

@{ name = "Java"; cmd="java --version"; min="17.0"; max="24.0" },
@{ name = "Maven"; cmd="mvn --version"; min="3.2"; max="4.0" },
@{ name = "Node.js"; cmd="node --version"; min="12.0"; max="24.0" },
@{ name = "Python"; cmd="python --version"; min="3.2"; max="3.14" },
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Python and pip are not required by default. Have in mind that the prereqs are not for building BTVA project itself but for building the projects generated by it's archetypes, e.g. vro js, vro ts, vra-ng, etc.
The general dependencies for all of them are mvn, java and node.
There is 1 specific project type that has additional dependencies - the polyglot (and abx) type of project supports the 3 types of actions, supported by vro - node, powershell and python. Based on the choosen action runtime you might need python or powershell as dependency.

So based on that I need to check with the team on how we want to handle this - throwing an error for missing python dependency on a regular JS based project would be misleading. maybe we can add a warning message for python and powershell that they might be required for polyglot project types.

@(
@{ name = "Java"; cmd="java --version"; min="17.0"; max="24.0" },
@{ name = "Maven"; cmd="mvn --version"; min="3.2"; max="4.0" },
@{ name = "Node.js"; cmd="node --version"; min="12.0"; max="24.0" },
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For node currently the officially supported version is 22. Some lower versions might work in specific use cases but it is situational so that cannot be officially supported.

# OpenSSL is not following the guidelines
@(
@{ name = "Java"; cmd="java --version"; min="17.0"; max="24.0" },
@{ name = "Maven"; cmd="mvn --version"; min="3.2"; max="4.0" },
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For maven it is a bit hard to say since maven seems to be more flexible, I've tested with 3.6 - 3.9. but don't know about other versions.

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

Labels

kind/enhancement Enhancement or improvement of existing features

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants