Skip to content

ROX-33733: Fix Next action enablement on policy wizard Actions step#19535

Open
clickboo wants to merge 1 commit intomasterfrom
boo-fix-rox-33733
Open

ROX-33733: Fix Next action enablement on policy wizard Actions step#19535
clickboo wants to merge 1 commit intomasterfrom
boo-fix-rox-33733

Conversation

@clickboo
Copy link
Contributor

@clickboo clickboo commented Mar 22, 2026

Description

In the policy creation/edit wizard, on the "Policy behavior > Actions" step, selecting "Inform and enforce" as the response method immediately enables the Next button even though no enforcement option (Build, Deploy, or Runtime) has been toggled on. The user can proceed to the Review step and the save button is greyed out, without any feedback as to why. A user then must press the Back button from the Review step and figure it out!

Expected behavior: The Next button should remain disabled until at least one enforcement toggle (Enforce on Build, Enforce on Deploy, or Enforce on Runtime) is enabled when "Inform and enforce" is selected.

User-facing documentation

Testing and quality

  • the change is production ready: the change is GA, or otherwise the functionality is gated by a feature flag
  • CI results are inspected

Automated testing

  • added unit tests
  • added e2e tests
  • added regression tests
  • added compatibility tests
  • modified existing tests

How I validated my change

CI + manual (pointing locally built UI to staging).
Screenshot before fix
Inform and Enforce selected, Next button activated without any enforce toggles selected
Screenshot 2026-03-22 at 1 12 39 PM

Screenshots after fix

  1. Grayed out Next button when Inform and Enforce is selected but no enforcement action toggle is - attached.
Screenshot 2026-03-22 at 1 09 16 PM

After Enforce on build toggled on, Next button is activated
Screenshot 2026-03-22 at 1 11 04 PM

@openshift-ci
Copy link

openshift-ci bot commented Mar 22, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@rhacs-bot
Copy link
Contributor

rhacs-bot commented Mar 22, 2026

Images are ready for the commit at 157d8fe.

To use with deploy scripts, first export MAIN_IMAGE_TAG=4.11.x-404-g157d8fe75a.

@clickboo clickboo requested a review from dvail March 22, 2026 07:43
@clickboo clickboo force-pushed the boo-fix-rox-33733 branch from fc25181 to 157d8fe Compare March 22, 2026 07:47
@clickboo
Copy link
Contributor Author

/test all

@codecov
Copy link

codecov bot commented Mar 22, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 49.26%. Comparing base (bff9977) to head (157d8fe).

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #19535   +/-   ##
=======================================
  Coverage   49.25%   49.26%           
=======================================
  Files        2727     2727           
  Lines      205788   205788           
=======================================
+ Hits       101362   101380   +18     
+ Misses      96890    96876   -14     
+ Partials     7536     7532    -4     
Flag Coverage Δ
go-unit-tests 49.26% <ø> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@clickboo clickboo marked this pull request as ready for review March 22, 2026 10:27
@clickboo clickboo requested a review from a team as a code owner March 22, 2026 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants