[New Resource]: aws_route53domains_ds_association for AssociateDelegationSignerToDomain

[bryceml]

Description

https://docs.aws.amazon.com/Route53/latest/APIReference/API_domains_AssociateDelegationSignerToDomain.html

https://awsapichanges.info/archive/changes/8c3630-route53domains.html

This was released recently, it would be nice if there were a way to use it through terraform. Not sure if it's better as its own resource, or if it's fine as part of the aws_route53domains_registered_domain resource. Since you can have multiple keys I'm guessing it would be better as it's own resource.

Requested Resource(s) and/or Data Source(s)

• aws_route53domains_ds_association

Potential Terraform Configuration

resource "aws_route53domains_ds_association" "example" {
  domain_name = aws_route53domains_registered_domain.example.domain_name
  algorithm   = aws_route53_key_signing_key.example.signing_algorithm_type # default value of 13
  flags       = aws_route53_key_signing_key.example.flag # default value of 257
  public_key  = aws_route53_key_signing_key.example.public_key
}

References

https://docs.aws.amazon.com/Route53/latest/APIReference/API_domains_AssociateDelegationSignerToDomain.html

https://awsapichanges.info/archive/changes/8c3630-route53domains.html

Would you like to implement a fix?

No

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[Szasza]

Hi @bryceml ,

I would be interested in working on this issue.

[bryceml]

@Szasza good to hear. Have you made any progress so far?

[Szasza]

@bryceml sorry for the delayed response, life happened. I will get to it in the next few days.

[Szasza]

@bryceml I have started working on the resource and is making good progress. However I will be AFK for a month from the end of the week. There is a good chance that I won't be able to open the PR beforehand.

[seanseth7]

@Szasza Is there any chance that you'll be putting up a PR soon? I could be interested in implementing this as my team would benefit from this resource in a feature we're working on.

[Szasza]

@seanseth7 my ETA for a PR would be sometime mid-October. Please feel free to implement it if you need it sooner, however please let me know if so, so there is no double-work done.

[seanseth7]

@Szasza Thanks for the quick response! I'll be sure to let you know if I decide to move forward with implementing myself.

[seanseth7]

@Szasza just a heads up that I started working on it in #33596. Not sure when I'll finish it, but hopefully soon. This is my first time contributing so still figuring things out.

[github-actions]

This functionality has been released in v5.34.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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.