[
https://issues.apache.org/jira/browse/TC-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Neuman updated TC-190:
----------------------------
Description:
The A and AAAA types in the Config -> ttls section of the CrConfig are a
different type than the A and AAAA values in the DeliveryService -> ttls
section of the CrConfig. In the config sections they are strings but in the DS
sections they are ints. Since goTM uses a common struct for TTLs, this causes
an parsing the CrConfig in goTM. The CrConfig should be updated so that the
types are consistent.
ttls in the Config sections:
"ttls": {
"A": "3600",
"DNSKEY": "30",
"DS": "30",
"SOA": "86400",
"NS": "3600",
"AAAA": "3600"
},
ttls in the DS section:
"ttls": {
"A": 30,
"SOA": "86400",
"NS": "3600",
"AAAA": 30
},
was:
The A and AAAA types in the Config -> ttls section of the CrConfig are a
different type than the A and AAAA values in the DeliveryService -> ttls
section of the CrConfig. In the config sections they are strings but in the DS
sections they are ints. Since goTM uses a common struct for TTLs, this causes
an parsing the CrConfig in goTM. The CrConfig should be updated so that the
types are consistent.
ttls in the Config sections:
{quote}
"ttls": {
"A": "3600",
"DNSKEY": "30",
"DS": "30",
"SOA": "86400",
"NS": "3600",
"AAAA": "3600"
},
{quote}
ttls in the DS section:
{quote}
"ttls": {
"A": 30,
"SOA": "86400",
"NS": "3600",
"AAAA": 30
},
{quote}
> TTL type mismatch in CrConfig
> -----------------------------
>
> Key: TC-190
> URL: https://issues.apache.org/jira/browse/TC-190
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
> Affects Versions: 2.0.0
> Reporter: David Neuman
> Assignee: David Neuman
> Fix For: 2.0.0, 2.1.0
>
>
> The A and AAAA types in the Config -> ttls section of the CrConfig are a
> different type than the A and AAAA values in the DeliveryService -> ttls
> section of the CrConfig. In the config sections they are strings but in the
> DS sections they are ints. Since goTM uses a common struct for TTLs, this
> causes an parsing the CrConfig in goTM. The CrConfig should be updated so
> that the types are consistent.
> ttls in the Config sections:
> "ttls": {
> "A": "3600",
> "DNSKEY": "30",
> "DS": "30",
> "SOA": "86400",
> "NS": "3600",
> "AAAA": "3600"
> },
> ttls in the DS section:
> "ttls": {
> "A": 30,
> "SOA": "86400",
> "NS": "3600",
> "AAAA": 30
> },
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
