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.
The default behavior is still to use --status-policy=all. The option is there for users that want to avoid the status behavior for various reasons. In our case, we use
kpt live apply
in our CI/CD pipelines, but don't need it saving statuses for all resources into the inventory. Thus, we want to be able to pass--status-policy=none
.I created a partner PR in kubernetes-sigs/cli-utils#637. The idea is to have that merged first and then rely on that flagutils func in this PR.
If this flag has been intentional withheld from users, can we consider having this flag hidden instead?