From 501ae886738522b13e3c9e8c5f564c48d5c135d8 Mon Sep 17 00:00:00 2001 From: Ella <72365100+eilla1@users.noreply.github.com> Date: Wed, 16 Jun 2021 15:25:14 -0700 Subject: [PATCH] chore: use = --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 3ad16d3..91e04eb 100644 --- a/README.md +++ b/README.md @@ -122,7 +122,7 @@ Further information can be found in [Records Documentation](/docs/records.md). We're ready to do a dry-run with our new setup to see what changes it would make. Since we're pretending here we'll act like there are no existing records for `example.com.` in our accounts on either provider. ```shell -$ octodns-sync --config-file ./config/production.yaml +$ octodns-sync --config-file=./config/production.yaml ... ******************************************************************************** * example.com. @@ -146,7 +146,7 @@ There will be other logging information presented on the screen, but successful Now it's time to tell OctoDNS to make things happen. We'll invoke it again with the same options and add a `--doit` on the end to tell it this time we actually want it to try and make the specified changes. ```shell -$ octodns-sync --config-file ./config/production.yaml --doit +$ octodns-sync --config-file=./config/production.yaml --doit ... ``` @@ -177,7 +177,7 @@ If that goes smoothly, you again see the expected changes, and verify them with Very few situations will involve starting with a blank slate which is why there's tooling built in to pull existing data out of providers into a matching config file. ```shell -$ octodns-dump --config-file ./config/production.yaml --output-dir tmp/ example.com. route53 +$ octodns-dump --config-file=config/production.yaml --output-dir=tmp/ example.com. route53 2017-03-15T13:33:34 INFO Manager __init__: config_file=tmp/production.yaml 2017-03-15T13:33:34 INFO Manager dump: zone=example.com., sources=('route53',) 2017-03-15T13:33:36 INFO Route53Provider[route53] populate: found 64 records