Repository navigation
KCL version migration tool support for rollbacking to v2 - #1813
Merged
Merged
Conversation
akidambisrinivasan
changed the title
akidambisrinivasan
had a problem deploying
to
manual-approval
September 10, 2026 16:49 — with 
GitHub Actions
Failure
GitHub Actions
Failure
For customers doing upgrade to KCLv3.5, they go through KCL v2 -> KCLv3.5 Client Version Phase1 -> KCLv3.5 Client Version Phase2 Phase 2 -> Phase 1 rollback is supported in tool and can be followed by a code rollback. However Phase 2 creates entries in lease table that is not backward compatible with KCLv2 and so rollback from Phase 2 -> KCL v2 required manual cleanup. This tool now supports --rollback-to-v2 mode which performs the cleanup so that the code rollback from Phase 2 -> KCL v2 can be safely performed
akidambisrinivasan
force-pushed
the
master
branch
from
September 10, 2026 18:31
784d744 to
9135700
Compare
chenylee-aws
approved these changes
Sep 10, 2026
akidambisrinivasan
had a problem deploying
to
manual-approval
September 10, 2026 18:58 — with
GitHub Actions
Failure
GitHub Actions
Failure
This branch had an error being deployed
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
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.
For customers doing upgrade to KCLv3.5, they go through KCL v2 -> KCLv3.5 Client Version Phase1 -> KCLv3.5 Client Version Phase2
Phase 2 -> Phase 1 rollback is supported in tool and can be followed by a code rollback.
However Phase 2 creates entries in lease table that is not backward compatible with KCLv2 and so rollback from Phase 2 -> Phase 1 -> KCL v2 required manual cleanup. This tool now supports --rollback-to-v2 mode which performs the cleanup so that the code rollback from Phase 2 -> Phase 1 -> KCL v2 can be safely performed
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.