✨ Add FieldValidation setting to client.Options#3393
✨ Add FieldValidation setting to client.Options#3393k8s-ci-robot merged 5 commits intokubernetes-sigs:mainfrom
Conversation
|
Hi @aerfio. Thanks for your PR. I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
accc52f to
c0cc0f7
Compare
c0cc0f7 to
6d79df3
Compare
|
/ok-to-test |
Co-authored-by: Alvaro Aleman <alvaroaleman@users.noreply.github.com>
Co-authored-by: Alvaro Aleman <alvaroaleman@users.noreply.github.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aerfio, alvaroaleman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
LGTM label has been added. DetailsGit tree hash: 98977a94cc541bcd689ec5c13be236ab440dfac7 |
This PR adds FieldValidation to client.Options:
Documentation explicitly lists only
Create,PatchandUpdate, because Apply methods do not accept FieldValidation argument in their Options, see https://pkg.go.dev/k8s.io/apimachinery@v0.34.2/pkg/apis/meta/v1#ApplyOptions. This is also reflected in current implementation.