jrushford edited a comment on pull request #5352: URL: https://github.com/apache/trafficcontrol/pull/5352#issuecomment-739093541
> ohhh, right. Yeah, it seems like it works like that. But I'm not sure which files are supposed to produce errors: > > ```shell > find ./test-files/etc/ -type f | while read file; do > echo ""; > echo "testing $file"; > ./plugin_verifier -c ./test-files/etc -p ./test-files/libexec/ "$file"; > done > ``` > > output > Some of them have "bad" in the name, so I expect the errors. Some don't, though, and I'm not sure if they're supposed to? You would only run it on a remap.config or plugin.config file as that is where you configure ats plugins. @ocket8888 you can only check one file at a time with **plugin_verifier**. You either name the file on the command line or pipe the contents of the file to the **plugin_verifier**. There are 6 test files in test-files/etc that you can run the **plugin_verifier** against, plugin.config, remap.config, remap-multiline.config, bad-plugin.config, bad-remap.config, or bad-remap-multiline.config. The files with **bad** in the name should give errors. The other 3 shouldn't. You can run the test on a file using this: ` $ ./plugin_verifier -c test-files/etc -p test-files/libexec test-files/etc/remap.config` or ` $cat test-files/etc/bad-remap.config | ./plugin_verifier -c test-files/etc -p test-files/libexec` Repeat for the other 6 files. In production, you would not need the options as the default plugin and config directories would be used as in: `./plugin_verifier /opt/trafficserver/etc/trafficserver/remap.config` or `cat /opt/trafficserver/etc/trafficserver/remap.config | ./plugin_verifier` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
