-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
✨ Client option types implement client option interfaces #589
✨ Client option types implement client option interfaces #589
Conversation
Happy to backport (IIRC, we haven't made any breaking changes yet, so releasing is going to be more-or-less just FF to master for a bit). Do you mind doing this for the rest of the options types too? That way we have consistency. |
But yeah, this seems pretty reasonable |
@DirectXMan12 updated the PR to make all the option types implement the corresponding interfaces. Obviously I am pretty late to the party to mention that, but I think there is a reason ppl commonly use option funcs and not option interfaces..We can probably think about that for a v0.3 |
399b8ac
to
b7dfffa
Compare
/test pull-controller-runtime-test |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alvaroaleman, DirectXMan12 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
@DirectXMan12 should I create a cherrypick PR for the release-0.2 branch? |
We'll pull it in as part of the next release -- we generally don't need to cherry-pick until we start breaking things, and I don't think we've merged anything breaking. You can do a release PR though -- just ask for a merge of master into release-0.2, and check the release notes by running $ git checkout release-0.2
$ git merge master
$ ./hack/release/release-notes.sh |
Kubebuilder Annotation Document
Currently setting multiple
ListOption
s is pretty annoying, because it is not defined as a function but as an interface, which can not be defined inline.This PR extends the existing
ListOptions
struct to implement theListOption
interface to allow using it as aListOption
.If anyhow possible, I'd be super, super glad if we could get this into the
release-0.2
branch as well 😬/assign @DirectXMan12