feat(cp): error when some targeted pods are not running#79
Merged
Conversation
Match exec's readiness check behavior: when multi-pod cp targets pods that aren't running, error with a list of non-ready pods and suggest --ready-only to proceed with only the running subset. Previously cp silently filtered to running pods, hiding partial failures. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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
cp, matchingexec's existing behavior--ready-onlyflag to opt into copying only to/from running podsTest plan
cpunit tests pass--ready-onlybypassokdev cp --allwith mixed-phase pods errors without--ready-onlyokdev cp --all --ready-onlysucceeds on running subset🤖 Generated with Claude Code