feat: Print skip reasons in live plan output - #4715
Open
vishnukothakapu wants to merge 1 commit into
Open
Conversation
This change captures the skip reason generated by cli-utils and prints it in the output of the kpt live plan command, improving the developer experience. Assisted-by: Antigravity:Gemini 3.1 Pro (High) Signed-off-by: Vishnu Kothakapu <vishnukothakapu27@gmail.com>
vishnukothakapu
requested review from
efiacor,
kispaljr,
liamfallon and
mozesl-nokia
as code owners
August 25, 2026 18:49
✅ Deploy Preview for kptdocs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
mozesl-nokia
approved these changes
Aug 26, 2026
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.
Description of the change
This PR updates the CLI output logic in
commands/alpha/live/plan/command.goand the event parsing inpkg/live/planner/cluster.goto properly capture and print the skip reason for resources that are skipped during actuation.Previously, skipped events with a reason attached to the
Errorfield were incorrectly classified as hard errors. They are now appropriately marked asSkipwith aSkipReason, and thekpt live planoutput prints this reason right below the resource.Motivation for the change
When managing complex applications, resources may be intentionally skipped during actuation due to specific annotations or missing references. Without a descriptive message explaining why the resource was skipped, developers and operators are left guessing if it was a configuration error, an intentional lifecycle hook, or a bug. This change improves transparency and developer experience by surfacing the skip reason provided by
cli-utils.Fixes
Fixes #4714