Skip to content

Adds first pass at env var only deployments#108

Open
bomoko wants to merge 5 commits intomainfrom
feature-env-only-deployments
Open

Adds first pass at env var only deployments#108
bomoko wants to merge 5 commits intomainfrom
feature-env-only-deployments

Conversation

@bomoko
Copy link
Contributor

@bomoko bomoko commented Dec 17, 2025

This adds a very, very rudimentary implementation of environment variable only deployments - primarily to show how/that it can be done in the UI very simply.

@bomoko bomoko marked this pull request as ready for review December 18, 2025 03:37
@bomoko bomoko requested review from CGoodwin90 and Copilot December 18, 2025 03:39
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR introduces a new deployment mode for environment variable-only deployments, providing users with the option to quickly apply variable changes without rebuilding container images. The implementation adds a mutation parameter to the GraphQL query and creates a new UI with card-based deployment type selection.

  • Extends the deployEnvironmentLatest mutation to accept an envVarOnly parameter that sets the LAGOON_VARIABLES_ONLY build variable
  • Introduces a card-based UI for selecting between "Full Deployment" and "Variables Only Deployment" modes
  • Displays a warning message when variables-only deployment is selected to inform users about limitations

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.

File Description
src/lib/mutation/deployEnvironmentLatest.ts Adds envVarOnly parameter and buildVariables array to pass LAGOON_VARIABLES_ONLY flag to the deployment API
src/components/pages/deployments/_components/DeployLatest.tsx Refactors deployment UI to show deployment type selection cards, adds state management for deployment type, and includes a warning for partial deployments

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@CGoodwin90
Copy link
Collaborator

Made a few small updates:

  • Updated CSS styling to Tailwind for consistency
  • Replaced the DeployOptionCard component with the existing Button components (Can look at creating an actionButton component in the UI-Library for this kind of use case)
  • Updated the loading state to match the new components & moved the logic out of DeployLatest and into the app router Loading

Everything else looks good

@bomoko
Copy link
Contributor Author

bomoko commented Dec 18, 2025

@CGoodwin90 okay - this is great - I guess this should only be merged AFTER the API becomes generally available. So after rollout.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants