Gurvinder Singh bfde429b8e add support CNAME for dns-01 challenge ...

Domain for which certificate is asked for can have a CNAME, so we should check it.
If domain has a CNAME, create the challange TXT record in the alias domain.

This is useful in the scenario where a company like us is using some DNS provider
which is not supported dynamically. We can then create a CNAME for records like

_acme-challenge.example.com -> example.aws.hosted.com

So this will allow us getting cert for *.example.com with creating txt record in route53 for above exxample.

2018-06-21 21:48:16 +02:00

..

api

Move to github.com/jetstack/cert-manager repo

2017-11-03 16:41:39 +00:00

apis

Run hack/update-codegen.sh

2018-06-08 15:48:30 +01:00

client

Run hack/update-codegen.sh

2018-03-23 18:30:49 +00:00

controller

issuers: Skip triggering API update if status has not changed

2018-06-18 01:55:45 +01:00

issuer

add support CNAME for dns-01 challenge

2018-06-21 21:48:16 +02:00

logs

Add e2e test framework and basic Issuer test

2017-09-08 16:25:21 +01:00

scheduler

Enable go race detector and fix race

2017-12-01 22:54:12 +00:00

util

Create common GenerateCSR and GenerateTemplate methods for creating Certificate/CertificateRequest

2018-06-08 15:15:27 +01:00