data.gov - updating dns #567
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Generation script gist at https://gist.github.com/robert-bryson/58351b0cd691ae002853fb68348e1b1a |
6 tasks
|
@JJediny yup, let's do it. |
Thanks for the heads up @davemcorwin! Working on a fix with #569 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to GSA/data.gov#1001
This PR configures data.gov DNS to use 18f/dns in the near future.
In order to configure DNSSEC, the
aws_route53_hosted_zone_dnssecresource is need from terraform-provider-aws. It was introduced in3.31.0so this PR updates the version currently used by 18f/dns (3.30.0) one minor version.3.30.0was released in March 2021, the current version is3.74.0.Data.gov is not a new site, so I believe the section below is not relevant.
@18F/oscfor review