From f92e168c174ab5752f9aaa0fe7e77541b71a9004 Mon Sep 17 00:00:00 2001 From: Vlad Voloshyn Date: Sun, 13 Jan 2019 20:30:01 +0200 Subject: [PATCH 1/4] Add description about default_ttl and enforce_order keys in config --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index a421301..6f2c195 100644 --- a/README.md +++ b/README.md @@ -35,6 +35,8 @@ providers: config: class: octodns.provider.yaml.YamlProvider directory: ./config + default_ttl: 3600 + enforce_order: True dyn: class: octodns.provider.dyn.DynProvider customer: 1234 @@ -56,6 +58,10 @@ zones: `class` is a special key that tells OctoDNS what python class should be loaded. Any other keys will be passed as configuration values to that provider. In general any sensitive or frequently rotated values should come from environmental variables. When OctoDNS sees a value that starts with `env/` it will look for that value in the process's environment and pass the result along. +`enforce_order` is a special key that tells OctoDNS to enforce sorting order on the yaml config. By default it is set to True. + +If you don't want to set same TTL each time for your records, you can optionally use `default_ttl` key - it will be used in records when not specified in the data. By default it is set to 3600 seconds. + Further information can be found in the `docstring` of each source and provider class. Now that we have something to tell OctoDNS about our providers & zones we need to tell it about or records. We'll keep it simple for now and just create a single `A` record at the top-level of the domain. From 772042f237b6e7642171295405ba2ce7f987596f Mon Sep 17 00:00:00 2001 From: Vlad Voloshyn Date: Sun, 13 Jan 2019 20:34:30 +0200 Subject: [PATCH 2/4] Use right value names in MX type records --- docs/records.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/records.md b/docs/records.md index 75f4d0b..a833d4b 100644 --- a/docs/records.md +++ b/docs/records.md @@ -120,10 +120,10 @@ In the above example each name had a single record, but there are cases where a - 1.2.3.5 - type: MX values: - - priority: 10 - value: mx1.example.com. - - priority: 10 - value: mx2.example.com. + - exchange: mx1.example.com. + preference: 10 + - exchange: mx2.example.com. + preference: 10 ``` ### Record data From bcc741604800b2ca7c8247ad14d9dadc01ba55f2 Mon Sep 17 00:00:00 2001 From: Vlad Voloshyn Date: Sun, 13 Jan 2019 22:17:19 +0200 Subject: [PATCH 3/4] Remove enforce_order and default_ttl description from README --- README.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/README.md b/README.md index 6f2c195..2451e70 100644 --- a/README.md +++ b/README.md @@ -58,10 +58,6 @@ zones: `class` is a special key that tells OctoDNS what python class should be loaded. Any other keys will be passed as configuration values to that provider. In general any sensitive or frequently rotated values should come from environmental variables. When OctoDNS sees a value that starts with `env/` it will look for that value in the process's environment and pass the result along. -`enforce_order` is a special key that tells OctoDNS to enforce sorting order on the yaml config. By default it is set to True. - -If you don't want to set same TTL each time for your records, you can optionally use `default_ttl` key - it will be used in records when not specified in the data. By default it is set to 3600 seconds. - Further information can be found in the `docstring` of each source and provider class. Now that we have something to tell OctoDNS about our providers & zones we need to tell it about or records. We'll keep it simple for now and just create a single `A` record at the top-level of the domain. From ca6b3c61106075c34653feef2767284d43b1f031 Mon Sep 17 00:00:00 2001 From: Ross McFarland Date: Mon, 28 Jan 2019 08:33:17 -0800 Subject: [PATCH 4/4] Version bump to 0.9.4 & CHANGELOG.md update --- CHANGELOG.md | 16 +++++++--------- octodns/__init__.py | 2 +- 2 files changed, 8 insertions(+), 10 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 0cdab51..87e70a0 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,13 +1,11 @@ -## v0.9.4 - ....-..-.. - Dynamic Records Beta +## v0.9.4 - 2019-01-28 - The one with a bunch of stuff, before the big one -* Dynamic Records (more powerful/flexible replacement for geo) - * Will support A, AAAA, and CNAME out the gate and include the ability to - weight records. It should provide a foundation for further suppport - if/when needed. - * Major refactoring and improvements to validation of the Record hierarchy, - things are much more consisntely implemented now and error messages should - be more actionable/clear. Both the base values and dynamic values use the - same validatio logic. +* A bunch of "dynamic" stuff that'll be detailed in the next release when + providers actually support it :grin: +* Route53Provider adds support for using session tokens +* Added support for proxying Cloudflare ALIAS records +* Dyn CAA TTL fix +* Documentation fixes and improvements * natsort version bump to address setup issues * DNSSimple TXT record handling fixes, ; it's always ; * Route53Provider support for sessiom tokens diff --git a/octodns/__init__.py b/octodns/__init__.py index 3f73cf3..6125bf1 100644 --- a/octodns/__init__.py +++ b/octodns/__init__.py @@ -3,4 +3,4 @@ from __future__ import absolute_import, division, print_function, \ unicode_literals -__VERSION__ = '0.9.3' +__VERSION__ = '0.9.4'