Scancentral SAST not enabled by default on 24.2 - EKS/Helm

[ruivit]

Current Behavior

When deploying version 24.2 of SSC and SC with Helm, Scancentral SAST is not enabled by default even when specified on the values file.

Scancentral SAST was enabled by default on version 23.1.

This is an issue since the documentation says that restart of server is required to apply the configuration, and on a deployment in Kubernetes this is not possible.

Expected Behavior

Scancentral SAST should be enabled by default and no restart should be needed.

Steps To Reproduce

1. Install SSC and SC via helm
   helm install fortify-sc -n fortify fortify/scancentral-sast --values=values.yml
   helm install ssc -n fortify fortify/fortify-ssc --values=values.yml

2. When going to the settings page, scancentral is not enabled by default
   

Environment

All Fortify components are on version 24.2
Helm - v3.15.3
Kubernetes - 1.29

Anything else?

It appears that documentation was updated on the last commit but the values files remained the same. I wonder if something changed between version which are not being documented.

[Timpartage1]

hello team, could you please help on this?