Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

etcdctl: add support for filtering by {min,max} x {create,mod} x {revision} #18233

Merged
merged 1 commit into from
Jul 2, 2024

Conversation

jcferretti
Copy link
Contributor

etcdctl is missing options to modify get opts for WithMinCreateRev, WithMaxCreateRev, WithMinModRev, WithMaxModRev.

@k8s-ci-robot
Copy link

Hi @jcferretti. Thanks for your PR.

I'm waiting for a etcd-io 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.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@jcferretti jcferretti changed the title Add support for filtering by {min,max} x {create,mod} x {revision} to etcdctl. etcdctl: add support for filtering by {min,max} x {create,mod} x {revision} Jun 25, 2024
@henrybear327
Copy link
Contributor

/ok-to-test

@jcferretti please remember to sign-off your commits! Thanks!

@jcferretti
Copy link
Contributor Author

/retest

Copy link
Member

@jmhbnz jmhbnz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - Thanks @jcferretti

Once merged please raise an update to changelog for 3.6.

tests/e2e/ctl_v3_kv_test.go Outdated Show resolved Hide resolved
@ahrtr
Copy link
Member

ahrtr commented Jul 2, 2024

It looks much better now. Please squash the commits.

@jcferretti
Copy link
Contributor Author

jcferretti commented Jul 2, 2024

It looks much better now. Please squash the commits.

I will do this, but I want to point out that this is strange. Github should squash on merge, so for the final result it shouldn't matter, and on the other hand review history and history of changes of the PR itself is lost.

So I don't understand why this would be (a) necessary (b) desirable.

@jcferretti jcferretti force-pushed the etcdctl-minmaxcreatemod branch 2 times, most recently from beb5526 to 11fb98b Compare July 2, 2024 16:38
…ision}

Signed-off-by: Cristian Ferretti <jcferretti2020@gmail.com>
@jcferretti
Copy link
Contributor Author

/retest

@ahrtr
Copy link
Member

ahrtr commented Jul 2, 2024

I will do this, but I want to point out that this is strange.

  • Nobody cares about your intermediate commits for such a simple PR.
  • Don't pollute the commit history.

Copy link
Member

@ahrtr ahrtr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ahrtr ahrtr merged commit 37cbd6c into etcd-io:main Jul 2, 2024
47 checks passed
@jcferretti
Copy link
Contributor Author

jcferretti commented Jul 2, 2024

  • Don't pollute the commit history.

How is the commit history going to be polluted if github squashes on merge?

https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

5 participants