* Allow for the DNSimple account ID to be specified via the dnssimple.accountID value
* Allow for the DNSimple account ID to be manually specified via the DNSIMPLE_ACCOUNT_ID environment variable
Fix incorrect variable specification in main.go
* Allow for the DNSimple account ID to be manually specified via the DNSIMPLE_ACCOUNT_ID environment variable
Fix missing return of nil in main.go
* Fix incorrect double-declaration of env section in deployment.yaml
* Fix incorrect logic when handling DNSIMPLE_ACCOUNT_ID environment variable
* The client.Zones.GetZone check isn't needed in the getExistingRecord function and it prevents User API tokens from being used for authentication - only Account API tokens would work
* Incorporate changes from https://github.com/puzzle/cert-manager-webhook-dnsimple/pull/29 so that the DNSimple accountID may be obtained from the Issuer config if a DNSimple User API token is being used
* Remove unused variable DnsimpleAccountId
* Fix deploy/dnsimple/templates/deployment.yaml - DNSIMPLE_ACCOUNT_ID environment variable doesn't do anything anymore so we can delete it
* Pass the .Values.dnsimple.accountID value down to the staging and production ClusterIssuer configs
* Update README.md with documentation on the dnsimple.accountID parameter
* The ClusterIssuer configs must quote the accountID value so that it is interpreted as a string and not as a number
* Fix indentation level of imagePullSecret in deployment.yaml
- Switch from apiregistration.k8s.io/v1beta1 to apiregistration.k8s.io/v1 where available
- Switch from rbac.authorization.k8s.io/v1beta1 to rbac.authorization.k8s.io/v1 where available
- Switch from cert-manager.io/v1alpha2 to cert-manager.io/v1 where available
Add variable image.pullSecret to Helm chart to support specifying an
image pull secret. This is mostly useful for people running an in-house
fork of cert-manager-webhook-dnsimple.
- Add variable dnsimple.existingTokenSecret to the Helm chart
to support using an existing secret. This is useful e.g. in
combination with https://github.com/bitnami-labs/sealed-secrets.
- Add variable dnsimple.tokenSecretName to support configuring the
name of the token secret.
When using a GitOps deployment model, these resources are always
considered "out of sync", as the resulting Certificate object's
'duration' field also specifies minutes & seconds.
These changes are essentially a no-op, but match the object, for
GitOps compatability.
