nwcs-sh

Results 3 issues of nwcs-sh

If query strings are "encoded", `*` is turned into `%2A`. This is not supported by vts, see below: ``` # curl '127.0.0.1:9001/status/control?cmd=reset&group=%2A' {"processingReturn":false,"processingCommandString":"reset","processingGroupString":"%2A","processingZoneString":"","processingCounts":0} # curl '127.0.0.1:9001/status/control?cmd=reset&group=*' {"processingReturn":true,"processingCommandString":"reset","processingGroupString":"*","processingZoneString":"","processingCounts":8} ```

enhancement

### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior Current behavior appears that auto id fields start at an arbitrary...

I have a heavily modified forked version of pcidb that uses embed for pci.ids; cant really send that as a PR as it'll break this which I do not want...