Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: documenting the flags issue in CAA record #384

Merged
merged 18 commits into from
Sep 30, 2023
Merged
41 changes: 28 additions & 13 deletions modules/dns/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,19 +3,34 @@
This module is used to create and manage IBM Cloud Internet Services (CIS) DNS records.


Although the SRV record name is provided in the variable, it is stored as `_service._proto.record_name.domain_name TTL class type of record priority weight port target`. For more information, see [What is a DNS SRV record?](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-srv-record/).


The changed name means that when you run a `terraform plan` command after a successful `terraform apply`, the output shows that the DNS record requires an update, as shown in the following example. However, your infrastructure will not be affected.

```
# module.cis_dns_records[0].ibm_cis_dns_record.dns_records["NAME/SRV"] will be updated in-place
~ resource "ibm_cis_dns_record" "dns_records" {
id = "a5177ec049fc2973a33df1441e869a27:9684838a87ecxxx5518:crn:v1:bluemix:public:internet-svcs:global:a/abac0df06b644axxx4f55b3880e:6ee7ec9a-5e68-4b6f-af9a-5714xxx4d::"
~ name = "_sip._udp.test-example.srv.test**.**.com" -> "test-example.srv"
# (13 unchanged attributes hidden)
}
```
1. Although the SRV record name is provided in the variable, it is stored as `_service._proto.record_name.domain_name TTL class type of record priority weight port target`. For more information, see [What is a DNS SRV record?](https://www.cloudflare.com/en-gb/learning/dns/dns-records/dns-srv-record/).


The changed name means that when you run a `terraform plan` command after a successful `terraform apply`, the output shows that the DNS record requires an update, as shown in the following example. However, your infrastructure will not be affected.

```
# module.cis_dns_records[0].ibm_cis_dns_record.dns_records["NAME/SRV"] will be updated in-place
~ resource "ibm_cis_dns_record" "dns_records" {
id = "a5177ec049fc2973a33df1441e869a27:9684838a87ecxxx5518:crn:v1:bluemix:public:internet-svcs:global:a/abac0df06b644axxx4f55b3880e:6ee7ec9a-5e68-4b6f-af9a-5714xxx4d::"
~ name = "_sip._udp.test-example.srv.test**.**.com" -> "test-example.srv"
# (13 unchanged attributes hidden)
}
```
2. When a DNS record of CAA type is added, the `flags` is automatically assigned.
iamar7 marked this conversation as resolved.
Show resolved Hide resolved

The assignment of flags means when you run a `terraform plan` command after a successful `terraform apply`, the output shows that the DNS record requires an update, as shown in the following example. However, your infrastructure will not be affected.

```
# module.cis_dns_records.ibm_cis_dns_record.dns_records["test-exmple.caa/CAA"] will be updated in-place
~ resource "ibm_cis_dns_record" "dns_records" {
~ data = {
- "flags" = "0" -> null
# (2 unchanged elements hidden)
}
id = "fcef7410xxxxxxbad23c5fd0e7581b7c:7e66xxxxxecc7e12ac908ca75445ad21:crn:v1:bluemix:public:internet-svcs:global:a/abac0df06b644axxxxx6e44f55b3880e:06240432-xxxx-40e7-9f9c-594dfbdfe208::"
# (12 unchanged attributes hidden)
}
```

<!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->
### Requirements
Expand Down