Closed sjackson0109 closed 6 months ago
Voting for Prioritization
Volunteering to Work on This Issue
Looks like the specific TLD requirements are violated...
TLDRulesViolation: [ADMIN.UK_CONTACT_TYPE is missing, OWNER.UK_CONTACT_TYPE is missing, TECH.UK_CONTACT_TYPE is missing, BILL.UK_CONTACT_TYPE is missing]
Thats 4x contact objects required:
And the terraform registry, for this provider module, this resource, and matching this version, shows only 3x supported blocks:
[Contact Blocks](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53domains_registered_domain#contact-blocks)
The admin_contact, registrant_contact and tech_contact blocks support the following:
..... following lines snipped....
Guess we need a different billing contact, and a comment to clarify owner=registrant.
Tring to fix this manually, looks like the TLD for .co.uk also asks for additional payload of the registrant
contact details too...
This may simply have been me not being aware of the additional payloads needed
revised...
contacts = {
0 = {
# many rows redacted
extra_params = {
UK_COMPANY_NUMBER = "00000000" # Matches UK Company Register (Companies House)
UK_CONTACT_TYPE = "PLC"
}
}
}
inside my contacts_blocks, i added a simple check for the TLD, .co.uk:
extra_params = substr(each.key,length(each.key)-6,6) == ".co.uk" ? try(var.contacts[each.value.contacts.registrant_key].extra_params, null) : null
Am afraid, same issue, even with the extra params populated correctly:
2024-02-03T15:00:40.887Z [DEBUG] provider.terraform-provider-aws_v5.34.0_x5.exe: HTTP Response Received: tf_provider_addr=registry.terraform.io/hashicorp/aws @module=aws http.response.header.x_amzn_requestid=e55d063b-212e-403a-b20b-db07ab2a153a rpc.system=aws-api tf_aws.signing_region="" tf_resource_type=aws_route53domains_registered_domain @caller=github.com/hashicorp/aws-sdk-go-base/v2@v2.0.0-beta.46/logging/tf_logger.go:45 http.response.header.content_type=application/x-amz-json-1.1 rpc.service="Route 53 Domains" tf_aws.sdk=aws-sdk-go-v2 aws.region=us-east-1 http.response.header.date="Sat, 03 Feb 2024 15:00:22 GMT" rpc.method=UpdateDomainContact
Hey @sjackson0109 👋 Thank you for taking the time to raise this! In triaging this, I happened upon the same extra_params
find that you did. If you haven't already, it might be worth using something like terraform console
to validate that the chain of functions you're using to populate extra_params
is evaluating as you're expecting it to.
If you're still having issues after that, are you able to provide debug logs (redacted as necessary) in case whoever picks this up needs that information?
Hi @justinretzolk - Thanks for the feedback, yes i managed to solve it using the extra_params, on my test domain. yet to push it to the customer who needed this work a month or two ago. Shame it wasn't so obvious from the tf registry documentation.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Terraform Core Version
1.6.6
AWS Provider Version
5.34.0
Affected Resource(s)
aws_route53_domains_registered_domain
Expected Behavior
When trying to mass-update 50+ domains, only the .co.uk domains failed with an error. They should update, just-the-same way as all the others (.com, .uk, .net, .international, .io).
Actual Behavior
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
TF
https://github.com/sjackson0109/tf-aws-route53-domains
TFVARS
Steps to Reproduce
terraform plan 2 changes
terraform apply -auto-approve 1 success, 1 failed
And yes i did all the email-verification stages.
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None