What if you did something like this? Parameter name: "header" Config file name: "test_file.config" Value: "none"
And then, if you wanted to explicitly change it, you could use: Parameter name: "header" Config file name: "test_file.config" Value: "default" The default, ofc, would be "default", since there's no compelling reason to go back and add the parameter everywhere automatically. This makes it a little clearer what's going on, and provides a bit of flexibility in the future, should we decide that we need a specialized header for a different set of files. On Tue, Jun 13, 2017 at 2:26 PM, Gelinas, Derek <[email protected]> wrote: > We've come across a use case in which we need to create a "take and bake" > file in traffic ops which cannot have the usual headers automatically added > to configuration files. Rather than hard-code a specific file type that > should not have these headers into the code, I'm thinking about adding a > filter during the take and bake process that, if a parameter with the > filename is encountered with the name "no_header", the header will not be > included. > > In practice, a file without headers would have the following parameters: > > Parameter name: location > Config file name: test_file.config > Value: /opt/trafficserver/etc/trafficserver > > Parameter name: data > Config file name: test_file.config > Value: rm -rf / > > Parameter name: no_header > Config file name: test_file.config > Value: [value ignored] > > Any thoughts on this? > > Derek
