Closed fsommar closed 3 months ago
Hi @fsommar. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/ok-to-test
/unassign
Thanks @fsommar
/approve /lgtm
(Let's see if I have permissions here!)
/assign seans3
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fsommar, justinsb, mortent
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Thank you @mortent! Can I get help with creating a tag to be used in https://github.com/kptdev/kpt/pull/4129?
cc @justinsb
I'll be doing some other changes for watch filtering soon, so I'll cut a cli-utils release afterwards.
As for kapply, I think adding a global flag is probably fine, if you add it and tests to exercise it.
Pending that cli-utils release, will kptdev/kpt#4129 be accepted if it pins cli-utils to the merge commit of this change, even if there is no release that has this change yet?
(We've been blocked on these PRs for over a month, and it doesn't feel like fun to block even more on some other, unrelated, work...)
There's a v0.36.0 of cli-utils released. I've upgraded to that version in my PR in kptdev/kpt: https://github.com/kptdev/kpt/pull/4129/commits/5c792649490fb69df8acb7d1c2d7104a88369d0a.
Hi 👋
This change is intended for Kpt. We use
kpt live apply
in our CI/CD pipelines, but we don't need it saving statuses for all resources into the inventory. We want to be able to pass--status-policy=none
.I considered adding support for changing the status-policy flag in kapply as well, but I couldn't think of a way to introduce the flag without introducing it for all subcommands, or copying the description across for the applicable subcommands. Let me know if you want me to implement the flag here too.