henet

Documentation

Index

• Constants
• func NewSolver() webhook.Solver
• type Client
  • func (client Client) CreateRecord(rec Record) error
  • func (client Client) DeleteRecord(rec Record) error
  • func (client Client) FindRecord(name string, data string) Record
  • func (client *Client) LoadRecords() error
  • func (client *Client) LoadZone(zone string) error
• type Config
• type Matcher
• type Record
  • func NewTXTRecord(name string, data string) Record
• type Solver
  • func (s *Solver) CleanUp(ch *v1alpha1.ChallengeRequest) error
  • func (s *Solver) Initialize(kubeClientConfig *rest.Config, stopCh <-chan struct{}) error
  • func (s *Solver) Name() string
  • func (s *Solver) Present(ch *v1alpha1.ChallengeRequest) error

Constants

const Url = "https://dns.he.net"

Functions

func NewSolver

func NewSolver() webhook.Solver

Types

type Client

type Client struct {
	Username string
	Password string
	ZoneId   string
	Records  []Record
}

func (Client) CreateRecord

func (client Client) CreateRecord(rec Record) error

func (Client) DeleteRecord

func (client Client) DeleteRecord(rec Record) error

func (Client) FindRecord

func (client Client) FindRecord(name string, data string) Record

func (*Client) LoadRecords

func (client *Client) LoadRecords() error

func (*Client) LoadZone

func (client *Client) LoadZone(zone string) error

type Config

type Config struct {
}

Config is a structure that is used to decode into when solving a DNS01 challenge.

This information is provided by cert-manager, and may be a reference to additional configuration that's needed to solve the challenge for this particular certificate or issuer.

This typically includes references to Secret resources containing DNS provider credentials, in cases where a 'multi-tenant' DNS solver is being created.

If you do *not* require per-issuer or per-certificate configuration to be provided to your webhook, you can skip decoding altogether in favour of using CLI flags or similar to provide configuration.

You should not include sensitive information here. If credentials need to be used by your provider here, you should reference a Kubernetes Secret resource and fetch these credentials using a Kubernetes clientset.

type Matcher

type Matcher func(*html.Node) bool

type Record

type Record struct {
	Id       string
	Name     string
	Type     string
	TTL      string
	Priority string
	Data     string
}

func NewTXTRecord

func NewTXTRecord(name string, data string) Record

type Solver

type Solver struct {
	// contains filtered or unexported fields
}

Solver implements the provider-specific logic needed to 'present' an ACME challenge TXT record for your own DNS provider. To do so, it must implement the `github.com/jetstack/cert-manager/pkg/acme/webhook.Solver` interface.

func (*Solver) CleanUp

func (s *Solver) CleanUp(ch *v1alpha1.ChallengeRequest) error

func (*Solver) Initialize

func (s *Solver) Initialize(kubeClientConfig *rest.Config, stopCh <-chan struct{}) error

func (*Solver) Name

func (s *Solver) Name() string

Name is used as the name for this DNS solver when referencing it on the ACME Issuer resource. This should be unique **within the group name**, i.e. you can have two solvers configured with the same Name() **so long as they do not co-exist within a single webhook deployment**. For example, `cloudflare` may be used as the name of a solver.

func (*Solver) Present

func (s *Solver) Present(ch *v1alpha1.ChallengeRequest) error

Present is responsible for actually presenting the DNS record with the DNS provider. This method should tolerate being called multiple times with the same value. cert-manager itself will later perform a self check to ensure that the solver has correctly configured the DNS provider.