📚 Add note that top-level Route53RoleArn still works

dflook · Jan 26, 2019 · ca0b1fd · ca0b1fd
1 parent 151036b
commit ca0b1fd
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 3 deletions.
diff --git a/.circleci/config.yml b/.circleci/config.yml
@@ -19,7 +19,7 @@ jobs:
           pip3 install --upgrade setuptools wheel twine pip
           python3 setup.py sdist bdist_wheel
 
-          twine upload --sign dist/*
+          twine upload --sign --skip-existing dist/*
 
     - store_artifacts:
         path: dist/

diff --git a/README.md b/README.md
@@ -29,8 +29,7 @@ If you are using troposphere you can install this resource as an extension using
 
     $ pip install troposphere_dns_certificate
 
-You can then import the Certificate resource from troposphere_dns_certificate.certificatemanager instead of 
-troposphere.certificatemanager. 
+You can then import the Certificate resource from troposphere_dns_certificate.certificatemanager instead of troposphere.certificatemanager. 
 
 cloudformation.py is an example of using troposphere to create a template with a Certificate resource. 
 
@@ -156,6 +155,9 @@ In some cases the account owning the hosted zone might be a different one than t
 To support this you can specify the domain validation option property `Route53RoleArn` with a role-ARN that should be 
 assumed before creating the records required for certificate validation.
 
+If a top-level Route53RoleArn property is specified it will be assumed when validating domains that don't contain a
+Route53RoleArn domain validation option property.
+
 ```yaml
 ExampleCertificate:
   Properties: