Andrew Dryga 4e821a3c30 fix(portal): Remove OneLeet CAA record (#6678) ...

The CAA can't be set for a domain that has a CNAME record, see
https://letsencrypt.org/docs/caa/

> Note also that CAA checking follows CNAME redirects, just like all
other DNS requests. If
“[community.example.org](http://community.example.org/)” is a CNAME to
“[example.forum.com](http://example.forum.com/)”, the CA will respect
any CAA records that are set on
“[example.forum.com](http://example.forum.com/)”. It is not allowed for
a domain name with a CNAME record to have any other records, so there
cannot be conflicts between CAA records on the original name and CAA
records on the target of the redirect.

2024-09-12 15:59:15 -06:00

..

environments

fix(portal): Remove OneLeet CAA record (#6678)

2024-09-12 15:59:15 -06:00

examples

docs: fix references to AWS and Azure example modules (#5829)

2024-07-11 16:10:12 +00:00

modules

fix(devops): Create SSL certs before destroy (#6607)

2024-09-05 14:35:16 -07:00

.gitignore

chore(infra): Use Regional Instance Group in the GCP NAT example (#4183)

2024-03-19 08:44:14 -06:00