-
Notifications
You must be signed in to change notification settings - Fork 419
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
Improve test case #5
base: master
Are you sure you want to change the base?
Conversation
cmoulliard
commented
May 29, 2019
- Ignore idea and _out directory
- Add missing dot end of the DNS name
- Update dependencies. To be controlled
- Uncomment email and ApiSecretRef
- Add script to fetch kubebuilder binaries
- Add DNS server. Set additional vars
Signed-off-by: Charles Moulliard <[email protected]>
Signed-off-by: Charles Moulliard <[email protected]>
Signed-off-by: Charles Moulliard <[email protected]>
Signed-off-by: Charles Moulliard <[email protected]>
Signed-off-by: Charles Moulliard <[email protected]>
Signed-off-by: Charles Moulliard <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cmoulliard If they are not already assigned, you can assign the PR to them by writing 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 |
…or : suite.go:49: error waiting for DNS record propagation: Could not determine authoritative nameservers for cert-manager-dns01-tests.example.com.
/assign @munnerz |
FYI. The link to the CONTRIBUTING guide is missing @munnerz -> https://github.com/jetstack/cert-manager-webhook-example/blob/master/CONTRIBUTING.md |
Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits. 📝 Please follow instructions in the contributing guide to update your commits with the DCO Full details of the Developer Certificate of Origin can be found at developercertificate.org. The list of commits missing DCO signoff:
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/test-infra repository. I understand the commands that are listed here. |
@munnerz Can you have a look to this ticket ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for putting this together and sorry for the delay 😬
I've added a few comments - mostly I think we should keep the example fairly generic and not start talking about the RFC2136 issuer here, as it could cause confusion for users getting started writing their own webhook.
//Email string `json:"email"` | ||
//APIKeySecretRef v1alpha1.SecretKeySelector `json:"apiKeySecretRef"` | ||
Email string `json:"email"` | ||
APIKeySecretRef certmanagerv1.SecretKeySelector `json:"apiKeySecretRef"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not all of these fields are required by all DNS provider types, hence keeping the contents here generic. Can you revert these changes, and if you feel there could be additional clarification as to what a user should do here then add comments to explain it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think that I included them or maybe this is because they were defined within one of the example of the cert manager project. So, do you suggest that we remove the fields Email
and APIKeySecretRef
?
|
||
var validConfig = cmapi.ACMEIssuerDNS01ProviderRFC2136{ | ||
Nameserver: server.ListenAddr(), | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Referencing the RFC2136 solver here is confusing to users, and also won't result in the RFC2136 issuer actually being used (as dns.NewFixture(&customDNSProviderSolver{}
is still called).
Having the binaries path set + the script to fetch those binaries is great, but I think this example should be generic and show a basic setup that needs a bit of modification or commenting/uncommenting of example lines to get things to work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, what do you suggest that we do then here ?
@cmoulliard: PR needs rebase. 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/test-infra repository. |