Closed
Conversation
…r-aware - Align template dropdown values with backend-supported templates - Rehydrate pipeline options when template changes to prevent invalid configs - Conditionally render runtime, install, test, and build inputs based on: - selected template (node_app, python_app, container_service) - enabled stages (build, test, deploy) - Hide provider-specific deployment fields unless deploy stage is enabled - Fix pipeline generator to emit runtime-specific setup steps: - Use setup-node only for node_app - Use setup-python only for python_app - Prevent Node.js steps from leaking into Python-generated YAML This ensures UI state, generated YAML, and backend expectations stay in sync and removes misleading or non-applicable configuration paths.
…r-aware - Align template dropdown values with backend-supported templates - Rehydrate pipeline options when template changes to prevent invalid configs - Conditionally render runtime, install, test, and build inputs based on: - selected template (node_app, python_app, container_service) - enabled stages (build, test, deploy) - Hide provider-specific deployment fields unless deploy stage is enabled - Fix pipeline generator to emit runtime-specific setup steps: - Use setup-node only for node_app - Use setup-python only for python_app - Prevent Node.js steps from leaking into Python-generated YAML This ensures UI state, generated YAML, and backend expectations stay in sync and removes misleading or non-applicable configuration paths.
lorencDedaj
approved these changes
Dec 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 fixes several UI → backend mismatches in the CI/CD configuration wizard by making pipeline options template-, stage-, and provider-aware. The result is a more accurate, predictable, and user-friendly pipeline configuration experience.
What Changed
🧩 Frontend (ConfigurePage)
• Template dropdown now only exposes backend-supported templates
• Pipeline options dynamically update when the template changes
• Runtime, install, test, and build inputs render only when relevant:
• Based on selected template
• Based on enabled stages (build/test/deploy)
• AWS deployment fields are hidden unless:
• Provider is AWS and
• Deploy stage is enabled
• Option labels and placeholders adapt to the selected template (Node vs Python)
🧠 State Management (Zustand)
• Template changes now rehydrate pipeline options with safe defaults
• Provider-specific fields (AWS/GCP) are preserved across template switches
• Prevents invalid combinations like npm commands on Python pipelines
⚙️ Backend (pipeline_generator)
• Runtime setup steps are now template-specific:
• actions/setup-node only for Node pipelines
• actions/setup-python only for Python pipelines
• Eliminates Node.js setup from Python-generated GitHub Actions YAML