feat: implement conditional build parameters flow based on template setting #18390
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR implements conditional logic for build parameter flows based on the
template_use_classic_parameter_flow
workspace setting. When this setting isfalse
, the system now directs users to the workspace settings page for ephemeral parameter configuration instead of using the inline popover.Changes
New Component
BuildParametersPopover
or shows theUpdateBuildParametersDialogExperimental
dialogUpdated Components
StartButton
andRestartButton
to useConditionalBuildParametersPopover
ConditionalBuildParametersPopover
ConditionalBuildParametersPopover
Behavior Changes
When
template_use_classic_parameter_flow
istrue
:BuildParametersPopover
behavior (no change)When
template_use_classic_parameter_flow
isfalse
:Rationale
This change addresses the requirement that ephemeral parameters may depend on values of non-ephemeral parameters. By directing users to the workspace settings page, they can see and configure all parameters in context, ensuring proper dependency handling.
Testing
The changes maintain backward compatibility - workspaces with
template_use_classic_parameter_flow: true
will continue to work exactly as before. The new flow only activates when the setting isfalse
.Related Issues
Addresses the need for better ephemeral parameter handling in the experimental parameter flow.