ROUTE53: Support Route53's ALIAS record type (#239) (#301)
* Stable comparison of metadata (#239)
Iterating over a map in Go never produces twice the same ordering.
Thus when comparing two metadata map with more than one key, the
`differ` is always finding differences.
To properly compare records metadata, we need to iterate the maps
in a deterministic way.
Signed-off-by: Brice Figureau <brice@daysofwonder.com>
* Support for Route53 ALIAS record type (#239)
Route53 ALIAS doesn't behave like a regular ALIAS, and is much more
limited as its target can only be some specific AWS resources or
another record in the same zone.
According to #239, this change adds a new directive R53_ALIAS which
implements this specific alias. This record type can only be used
with the Route53 provider.
This directive usage looks like this:
```js
D("example.com", REGISTRAR, DnsProvider("ROUTE53"),
R53_ALIAS("foo1", "A", "bar") // record in same zone
R53_ALIAS("foo2", "A",
"blahblah.elasticloadbalancing.us-west-1.amazonaws.com",
R53_ZONE('Z368ELLRRE2KJ0')) // ELB in us-west-1
```
Unfortunately, Route53 requires indicating the hosted zone id
where the target is defined (those are listed in AWS documentation,
see the R53_ALIAS documentation for links).
2018-01-16 11:53:12 +01:00
---
name: R53_ZONE
parameters:
- zone_id
2023-01-12 16:59:42 -05:00
parameter_types:
zone_id: string
ts_return: DomainModifier & RecordModifier
2022-10-28 17:27:06 +02:00
provider: ROUTE53
ROUTE53: Support Route53's ALIAS record type (#239) (#301)
* Stable comparison of metadata (#239)
Iterating over a map in Go never produces twice the same ordering.
Thus when comparing two metadata map with more than one key, the
`differ` is always finding differences.
To properly compare records metadata, we need to iterate the maps
in a deterministic way.
Signed-off-by: Brice Figureau <brice@daysofwonder.com>
* Support for Route53 ALIAS record type (#239)
Route53 ALIAS doesn't behave like a regular ALIAS, and is much more
limited as its target can only be some specific AWS resources or
another record in the same zone.
According to #239, this change adds a new directive R53_ALIAS which
implements this specific alias. This record type can only be used
with the Route53 provider.
This directive usage looks like this:
```js
D("example.com", REGISTRAR, DnsProvider("ROUTE53"),
R53_ALIAS("foo1", "A", "bar") // record in same zone
R53_ALIAS("foo2", "A",
"blahblah.elasticloadbalancing.us-west-1.amazonaws.com",
R53_ZONE('Z368ELLRRE2KJ0')) // ELB in us-west-1
```
Unfortunately, Route53 requires indicating the hosted zone id
where the target is defined (those are listed in AWS documentation,
see the R53_ALIAS documentation for links).
2018-01-16 11:53:12 +01:00
---
2023-05-20 19:19:55 +02:00
`R53_ZONE` lets you specify the AWS Zone ID for an entire domain ([`D()` ](../global/D.md )) or a specific [`R53_ALIAS()` ](../domain/R53_ALIAS.md ) record.
2021-09-02 22:54:54 +02:00
2023-05-20 19:19:55 +02:00
When used with [`D()` ](../global/D.md ), it sets the zone id of the domain. This can be used to differentiate between split horizon domains in public and private zones. See this [example ](../../providers/route53.md#split-horizon ) in the [Amazon Route 53 provider page ](../../providers/route53.md ).
2021-09-02 22:54:54 +02:00
2023-05-20 19:19:55 +02:00
When used with [`R53_ALIAS()` ](../domain/R53_ALIAS.md ) it sets the required Route53 hosted zone id in a R53_ALIAS record. See [`R53_ALIAS()` ](../domain/R53_ALIAS.md ) documentation for details.
