Preliminary version. The functionality may change, and an upgrade may require manual migration actions.
Some features of Deckhouse Code ship turned off, and an administrator turns each one on with an instance-level feature flag. The “Edition” column names the editions in which a turned-on flag takes effect; every flag takes effect in the trial mode described on the License page.
Feature flags
| Flag | Edition | What it opens | Documentation |
|---|---|---|---|
fe_ | EE | The "Policies" pages of groups and projects, scan execution policies and the scans they mandate (SAST with Opengrep, secret detection with Gitleaks, Trivy, CodeScoring, PT AI and AppSec.Hub when appsec_hub_integration is enabled), scheduled scans, the CodeScoring and PT AI integrations, the "Dependency list" and "License compliance" pages | |
defect_ | EE | The DefectDojo integration and the upload of security reports to DefectDojo | |
appsec_ | EE | Project integration with AppSec.Hub, AppSec.Hub scans defined in scan execution policies, and uploading project scanner reports to AppSec.Hub. AppSec.Hub scans also require the fe_security_scan_policies feature flag | |
fe_ | EE | Pipeline execution policies, scheduled ones included. Takes effect only together with fe_security_scan_policies | |
fe_ | SE, EE | The Jaga integration, the Jaga push rules and the Jaga merge check | |
work_ | SE, EE | The REST API of work items, including the weight, health status and blocking links of epics, issues and other work items. |
Turning a flag on and off
Turn a flag on with gitlab-rails runner, replacing <FLAG> with the flag name:
- Linux package
- Omnibus Docker
- Helm Chart
- Deckhouse Platform module
sudo gitlab-rails runner 'Feature.enable(:<FLAG>)'docker exec code gitlab-rails runner 'Feature.enable(:<FLAG>)'d8 k -n code exec deploy/code-toolbox -- gitlab-rails runner 'Feature.enable(:<FLAG>)'d8 k -n d8-code exec -c toolbox deploy/toolbox -- gitlab-rails runner 'Feature.enable(:<FLAG>)'To turn a flag off, run the same command with Feature.disable(:<FLAG>).