Clean questions.yaml variable once the selected type is not selected anymore #10815
Labels
area/kubewarden
kind/enhancement
QA/dev-automation
Issues that engineers have written automation around so QA doesn't have look at this
Is your feature request related to a problem? Please describe.
When using questions.yaml, sometimes there is the need to configure mutually exclusive fields of values.yaml.
This blocks exposing affinity/anti-affinity, PodDisruptionBudgets, limits/requests, and others for Kubewarden charts.
To Reproduce
Describe the solution you'd like
A way to select between several mutual exclusive types in questions.yaml. Selecting one clears the value from the others.
Describe alternatives you've considered
The closest seem to be
type: radio
, and subquestions. This would allow for the subquestions to be of different types as needed.Yet, there's no way to input a value from selecting one of the radio options, as it works as an enum.
I've tried using
type: radio
with subquestions here, yet of course don't clean previous variables.See here:
Screencast_2024-04-16_16.25.26.webm
To reproduce, install
kubewarden-controller
chart orkubewarden-defaults
chart and see its questions, from the following:prod-questions-archive
See questions.yaml here.
Additional context
The text was updated successfully, but these errors were encountered: