fix: main_domain
option doesn't work for testnet
#206
Merged
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.
This PR fixes errors preventing DNS registration when using testnet config. Together with this PR to the config, it should resolve DNS errors for testnet.
Issue being fixed or feature implemented
Terraform was failing with:
What was done?
public_network_name
in variable by specifyingNETWORK_DEVNET_NAME
with non-devnet networks>=
operator instead of>
to ensure count is1
when creatingaws_elb
This should result in tuples for
aws_elb.web[0].dns_name
existing when subsequently attempting to create routes.How Has This Been Tested?
dash-network list testnet
works again,dash-network deploy -i testnet
indicates it will deploy records correctly as follows:Breaking Changes
None
Checklist:
For repository code-owners and collaborators only