From b1e762dee8ae235fa0d02f9d2468045124041c6e Mon Sep 17 00:00:00 2001 From: Chris Wells Date: Wed, 24 May 2017 16:33:44 -0400 Subject: [PATCH] Fixing octodns/record.py link --- docs/records.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/records.md b/docs/records.md index 2642470..d991311 100644 --- a/docs/records.md +++ b/docs/records.md @@ -79,6 +79,6 @@ In the above example each name had a single record, but there are cases where a ### Record data -Each record type has a corresponding set of required data. The easiest way to determine what's required is probably to look at the record object in [`octodns/records.py`](/octodns/records.py). You may also utilize `octodns-validate` which will throw errors about what's missing when run. +Each record type has a corresponding set of required data. The easiest way to determine what's required is probably to look at the record object in [`octodns/record.py`](/octodns/record.py). You may also utilize `octodns-validate` which will throw errors about what's missing when run. `type` is required for all records. `ttl` is optional. When TTL is not specified the `YamlProvider`'s default will be used. In any situation where an array of `values` can be used you can opt to go with `value` as a single item if there's only one.