Go version of GET servers/{server-name-or-id}/configfiles/ats does not return hdr_rw_mid.config files for mids

[mitchell852]

I'm submitting a ...

• bug report
• new feature / enhancement request
• improvement request (usability, performance, tech debt, etc.)
• other

Traffic Control components affected ...

• CDN in a Box
• Documentation
• Grove
• Traffic Control Client
• Traffic Monitor
• Traffic Ops
• Traffic Ops ORT
• Traffic Portal
• Traffic Router
• Traffic Stats
• Traffic Vault
• unknown

Current behavior:

When Mid Header Rewrite Rules are applied to a DS, a parameter is created as such:

name: location
configFile: hdr_rw_mid_xml-id.config
value: /opt/trafficserver/etc/trafficserver
secure: false

and that parameter is attached to the profile(s) of the mids employed by the delivery service. (which i believe is simply all the mids in the same cdn as the DS)

This ensures that when updates are queued on these mids, the hdr_rw_mid* file will be fetched, however, the following API call does not include the hdr_rw_mid* file:

GET api/1.1/servers/{mid-server-name-or-id}/configfiles/ats

Expected / new behavior:

The expected behavior is to pull any hdr_rw_mid* files as defined by the location parameters of the mid's profile as the Perl version of the endpoint did.

Minimal reproduction of the problem with instructions:

1. Identify a delivery service that employs the mid-tier (I.e. DNS) and note the xml-id
2. Add an entry to Mid Header Rewrite Rules; Save.
3. Ensure that a location parameter was created by navigating to https://tp.domain.net/#!/parameters and search for hdr_rw_mid_xml-id.config and note which profile(s) the parameter was attached to.
4. navigate to a mid employed by the ds (see next section) and click view config files. notice that hdr_rw_mid_xml-id.config does not show up in the list.

The call to GET api/1.1/servers/{mid-server-name-or-id}/configfiles/ats does not include ANY hdr_rw_mid files where the Perl version does.

Anything else:

How do I find a mid employed by the DS? Good question. You can do the following:

1. In TP, navigate to a DS
2. select manage servers
3. click the first server
4. on the server page, click view details for the server's cache group
5. on the server's cache group page, click view details for the parent cache group. now you are in the parent cache group or the mid cache group.
6. select view servers
7. select any mid server