-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Ability to roll back service deployments #1986
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Siumauricio
wants to merge
11
commits into
canary
Choose a base branch
from
319-ability-to-roll-back-service-depoyments
base: canary
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
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
…e schema updates - Added ShowEnv and ShowRollbackSettings components for displaying and configuring rollback settings. - Implemented ShowRollbacks component to list and manage rollbacks for applications. - Created rollback database schema and updated application schema to include rollback settings. - Added API routes for managing rollbacks, including fetching, creating, and deleting rollbacks. - Integrated rollback functionality into the application deployment process.
- Deleted SQL files for rollback table and related schema changes. - Removed corresponding snapshot files to clean up the database schema history.
…a updates - Created a new "rollback" table to manage rollback operations. - Added "rollbackActive" and "limitRollback" columns to the "application" table to support rollback features. - Established foreign key constraints between the "rollback" and "application" tables for data integrity.
…ema changes - Updated Tailwind configuration for responsive design. - Modified the ShowDeployments component to include rollback settings and actions. - Introduced a new "rollback" table in the database schema with foreign key relationships. - Updated deployment and application schemas to support rollback features. - Added rollback mutation to the API for initiating rollbacks.
- Enhanced the ShowDeployments component to conditionally display rollback options based on deployment status and type. - Removed the ShowRollbacks component and its references from the application, streamlining the UI and functionality.
- Replaced the ArrowDownToLine icon with RefreshCcw in the rollback button for improved clarity. - Cleaned up unused imports from the component to streamline the code.
…ctionality - Introduced a new "fullContext" JSONB column in the "rollback" table to store additional context for rollbacks. - Removed the "env" column from the "rollback" table to streamline data management. - Updated the rollbacks service to handle the new "fullContext" field during rollback creation. - Adjusted the application service to eliminate environment variable handling in rollback operations.
- Introduced "limitRollback" and "rollbackActive" properties to the base application configuration in both drop and traefik test files. - These additions enhance the rollback functionality by allowing configuration of rollback limits and activation status.
- Modified the command in the cleanUpSystemPrune function to remove the '--all' flag, streamlining the Docker system prune operation.
awesome feature! |
…UI components - Eliminated the "limitRollback" property from the application schema and the ShowRollbackSettings component, streamlining rollback configuration. - Updated the database schema to drop the "limitRollback" column from the "application" table, ensuring consistency across the application.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Introduce rollbacks for applications:
Close #319