mirror of
https://github.com/StackExchange/dnscontrol.git
synced 2024-05-11 05:55:12 +00:00
HEXONET: Add GHA tests. Update docs. (#942)
This commit is contained in:
6
.github/workflows/build.yml
vendored
6
.github/workflows/build.yml
vendored
@@ -30,7 +30,7 @@ jobs:
|
|||||||
strategy:
|
strategy:
|
||||||
fail-fast: false
|
fail-fast: false
|
||||||
matrix:
|
matrix:
|
||||||
provider: [AZURE_DNS, BIND, CLOUDFLAREAPI, DIGITALOCEAN, GANDI_V5, GCLOUD, NAMEDOTCOM, ROUTE53]
|
provider: [AZURE_DNS, BIND, CLOUDFLAREAPI, DIGITALOCEAN, GANDI_V5, GCLOUD, HEXONET, NAMEDOTCOM, ROUTE53]
|
||||||
exclude:
|
exclude:
|
||||||
- provider: DIGITALOCEAN # remove when #636 is fixed
|
- provider: DIGITALOCEAN # remove when #636 is fixed
|
||||||
steps:
|
steps:
|
||||||
@@ -63,6 +63,10 @@ jobs:
|
|||||||
GCLOUD_EMAIL: dnscontrol@dnscontrol-dev.iam.gserviceaccount.com
|
GCLOUD_EMAIL: dnscontrol@dnscontrol-dev.iam.gserviceaccount.com
|
||||||
GCLOUD_PROJECT: dnscontrol-dev
|
GCLOUD_PROJECT: dnscontrol-dev
|
||||||
GCLOUD_PRIVATEKEY: ${{ secrets.GCLOUD_PRIVATEKEY }}
|
GCLOUD_PRIVATEKEY: ${{ secrets.GCLOUD_PRIVATEKEY }}
|
||||||
|
HEXONET_DOMAIN : a-b-c-movies.com
|
||||||
|
HEXONET_ENTITY : OTE
|
||||||
|
HEXONET_PW : test.passw0rd
|
||||||
|
HEXONET_UID : test.user
|
||||||
NAMEDOTCOM_DOMAIN: dnscontrol-ndc.com
|
NAMEDOTCOM_DOMAIN: dnscontrol-ndc.com
|
||||||
NAMEDOTCOM_URL: api.name.com
|
NAMEDOTCOM_URL: api.name.com
|
||||||
NAMEDOTCOM_USER: dnscontroltest
|
NAMEDOTCOM_USER: dnscontroltest
|
||||||
|
@@ -91,15 +91,13 @@ yourself.)
|
|||||||
Pick a similar provider as your base. Providers basically fall
|
Pick a similar provider as your base. Providers basically fall
|
||||||
into three general categories:
|
into three general categories:
|
||||||
|
|
||||||
* **zone:** The API requires you to upload the entire zone every time. (BIND).
|
* **zone:** The API requires you to upload the entire zone every time. (BIND, NAMECHEAP).
|
||||||
* **incremental-record:** The API lets you add/change/delete individual DNS records. (ACTIVEDIR, CLOUDFLARE, DNSIMPLE, NAMEDOTCOM, GCLOUD, ROUTE53)
|
* **incremental-record:** The API lets you add/change/delete individual DNS records. (ACTIVEDIR, CLOUDFLARE, DNSIMPLE, NAMEDOTCOM, GCLOUD, HEXONET)
|
||||||
* **incremental-label:** Like incremental-record, but if there are
|
* **incremental-label:** Like incremental-record, but if there are
|
||||||
multiple records on a label (for example, example www.example.com
|
multiple records on a label (for example, example www.example.com
|
||||||
has A and MX records), you have to replace all the records at that
|
has A and MX records), you have to replace all the records at that
|
||||||
label. (GANDI_V5)
|
label. (GANDI_V5)
|
||||||
* **incremental-label-type:** Like incremental-record, but updates to any records at a label have to be done by type. For example, if a label (www.example.com) has many A and MX records, even the smallest change to one of the A records requires replacing all the A records. Any changes to the MX records requires replacing all the MX records. If an A record is converted to a CNAME, one must remove all the A records in one call, and add the CNAME record with another call. This is deceptively difficult to get right; if you have the voice between incremental-label-type and incremental-label, pick incremental-label. (DESEC)
|
* **incremental-label-type:** Like incremental-record, but updates to any records at a label have to be done by type. For example, if a label (www.example.com) has many A and MX records, even the smallest change to one of the A records requires replacing all the A records. Any changes to the MX records requires replacing all the MX records. If an A record is converted to a CNAME, one must remove all the A records in one call, and add the CNAME record with another call. This is deceptively difficult to get right; if you have the choice between incremental-label-type and incremental-label, pick incremental-label. (DESEC, ROUTE53)
|
||||||
|
|
||||||
TODO: Categorize NAMECHEAP
|
|
||||||
|
|
||||||
All providers use the "diff" module to detect differences. It takes
|
All providers use the "diff" module to detect differences. It takes
|
||||||
two zones and returns records that are unchanged, created, deleted,
|
two zones and returns records that are unchanged, created, deleted,
|
||||||
|
Reference in New Issue
Block a user