Using the dns-delegated component

[jessegonzalez]

NOTE: This was originally posted in sweetops.slack.com but was asked to post here and has been slightly modified from the original for additional context and clarity.

This is a followup to discussion #28.

The module interface for dns-delegated accepts a map as zone_config to define delegated subdomains. If I use this component as follows:

components:
  terraform:
    dns-delegated:
      metadata:
        type: real
      vars:
        zone_config:
          - subdomain: stg
            zone_name: example.com
          - subdomain: stg
            zone_name: example.internal
        request_acm_certificate: true
        dns_private_zone_enabled: false

I have the following observations:

Observation 1:

The dns-delgated interface does not allow for creation of both private and public zones with the avialable zone_config interface.

Observation 2:

The module does not appear to properly handle the above zone_config input using the zipmap function in locals:

zone_map = zipmap(var.zone_config[*].subdomain, var.zone_config[*].zone_name)

## this becomes
## zipmap (["stg", "stg"], ["example.com", "example.internal"])
##
## and ultimately
## {
##   "stg" = "example.internal"  
## }

Observation 3:

There are a handful of references in cloudposse-terraform-components usinga hardcoded remote_state references to dns-delegated.

But as you pointed out in the post by @Pablo Paez, you are working to eliminate that this year.

Questions:

• Since we do need both private and public hosted zones, is the recommended approach here to use the multiple component instances pattern? Something like following:

components:
  terraform:
    dns-delegated/private:
      metadata:
        type: real
        component: dns-delgated 

      vars:
        zone_config:
          - subdomain: stg
            zone_name: example.internal
        request_acm_certificate: true
        dns_private_zone_enabled: true

    dns-delegated/public:
      metadata:
        type: real
        component: dns-delgated 

      vars:
        zone_config:
          - subdomain: stg
            zone_name: example.com
        request_acm_certificate: true
        dns_private_zone_enabled: false

[GabisCampana]

@milldr

[milldr]

Since we do need both private and public hosted zones, is the recommended approach here to use the multiple component instances pattern?

Yes that's exactly correct. We have done the same with a few customers

As you pointed out, some components have hard-coded references to dns-delegated or dns-primary, so ensure you update them to align with your custom component names. We handle these on a case-by-case basis as they come up and welcome community pull requests for any that might be overlooked!

[osterman]

@jessegonzalez does this answer your questions?

[jessegonzalez]

Great to hear, this is the path I took.

I do see an opportunity to provide pull request to support observations 1 & 2. I'll review the contributing guidelines and go from there.