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.
When making changes to the
dnssec_config
of the dns module, thedns_keys
output is retrieved before the changes to the dns zone.Not only this means it takes two
terraform apply
to converge, but this is an issue when you enable dnssec and expect to find ads_record
in the output (to create a DS recordset).For example, create a test public zone without dnssec enabled:
This outputs the following, as expected:
Then, enable dnssec:
After one run, the output changes because the dnssec state variable is now "on", but the keys themselves are null:
A second run finally updates the output:
With the dependency, the
dns_keys
are retrieved after the zone is modified, and the output contains the keys from the first apply.Checklist
I applicable, I acknowledge that I have:
terraform fmt
on all modified filestools/tfdoc.py