fix: allow version pass to avoid latest install always

[misba7]

closes #8513

[iromli]

@misba7 What's the default JANS_VERSION?

[iromli]

@misba7 have we handle empty $JANS_VERSION?

[misba7]

empty JANS_VERSION installs latest, which was the default behavior.
I added the variable to be able to override it as needed.

[iromli]

did you mean command like helm install --version= (empty JANS_VERSION) also work?

[iromli]

ignore my last comment, i have tested it. The --version= <other-ops> is working while --version <other-ops> is not.

[dryrunsecurity]

DryRun Security Summary

The changes in the startjanssendemo.sh file aim to improve the deployment and configuration options for the Janssen IAM platform, including support for different persistence types, version selection, Istio integration, and customizable logging, providing more flexibility and security-conscious features for the Janssen deployment.

Expand for full summary

Summary:

The code changes in the startjanssendemo.sh file are focused on improving the deployment and configuration
options for the Janssen application, an open-source identity and access management (IAM) platform. The key
changes include support for different persistence types (LDAP, MySQL, PostgreSQL), the ability to specify
the Janssen version, integration with the Istio service mesh, and customizable logging configurations.

From an application security perspective, these changes are generally positive, as they provide more
flexibility and security-conscious features for the Janssen deployment. The support for different persistence
types allows the deployment to be tailored to the specific requirements of the environment, while the logging
configuration options help control the exposure of sensitive information. The integration with Istio can also
provide additional security benefits, such as mutual TLS (mTLS) between services, traffic monitoring, and
access control. However, it's important to ensure that the database credentials and configurations are properly
secured, especially for the MySQL and PostgreSQL options, and that Istio is properly configured and maintained
to maximize the security benefits.

Files Changed:

• automation/startjanssendemo.sh: This script has been updated to support different persistence types
  for the Janssen application, including LDAP, MySQL, and PostgreSQL. The user is prompted to enter the
  desired persistence type, and the script generates the appropriate configuration. The script also allows
  the user to specify the version of the Janssen application to be deployed, integrates with the Istio
  service mesh, and sets up customizable logging configurations for various Janssen components.

Code Analysis

We ran 7 analyzers against 1 file and 0 analyzers had findings. 7 analyzers had no findings.

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.