oscap: lock the wizard step behind a feature flag

The oscap feature have been quite eagerly pushed forward and it seems we
went a bit fast with it. To take more time and make sure all the
stakeholders agree on the way forward the decision was taken to put this
functionality behind a feature flag.

The two feature flags for both stage and prod are there:
* https://insights-stage.unleash.devshift.net/projects/default/features/image-builder.wizard.oscap.enabled (enabled on stage so we can test the feature)
* https://insights.unleash.devshift.net/projects/default/features/image-builder.wizard.oscap.enabled (disabled on prod)
This commit is contained in:
Thomas Lavocat 2023-10-17 17:18:08 +02:00 committed by Klara Simickova
parent 3984971a72
commit d60c6cb74b
4 changed files with 27 additions and 10 deletions

View file

@ -1,7 +1,7 @@
import isRhel from '../../../Utilities/isRhel.js';
const imageOutputStepMapper = (
{ 'target-environment': targetEnv, release, isBeta } = {},
{ 'target-environment': targetEnv, release, enableOscap } = {},
{ skipAws, skipGoogle, skipAzure } = {}
) => {
if (!skipAws && targetEnv?.aws) {
@ -19,7 +19,7 @@ const imageOutputStepMapper = (
if (isRhel(release)) {
return 'registration';
}
if (isBeta) {
if (enableOscap) {
return 'Compliance';
}
return 'File system configuration';

View file

@ -70,7 +70,7 @@ const registrationStep = {
),
name: 'registration',
nextStep: ({ values }) => {
if (values.isBeta) {
if (values.enableOscap) {
return 'Compliance';
} else {
return 'File system configuration';