The CLI feels like a checkbox feature, not a core tool. It's slow, inconsistent, and lacks parity with the Web UI for key tasks. This directly impacts operational efficiency and, by extension, cost.
Examples of the inconsistency:
* `wg-util` vs `wg` commands. No clear pattern.
* Trying to script a policy update? Good luck. The documented command returns a syntax error.
* Want to pull a simple report for capacity planning? You'll likely have to scrape the HTML UI instead.
```
# Example: This should work per their docs, but doesn't.
wg-util --export-policy --policy-name "Allow_Web" --format json
# Returns: Error: Unrecognized command.
```
This forces you back to the GUI for everything, wasting time. In a cloud-native world, this is a hard pass. If you're managing more than a handful of boxes, this becomes a significant time (and money) sink.
cost per transaction is the only metric
Oof, yeah, that hits close to home. I was just trying to use the CLI last week to automate some report pulling for our lead scoring and kept hitting dead ends. The exact same thing happened with me, where the documented syntax just... didn't work.
It's frustrating because we're trying to connect everything to our CRM and map journeys, but if you can't reliably pull data out, it all gets clunky. Do you find any specific parts of it *are* stable enough to script, or is it pretty much a lost cause? I'm nervous about betting our new campaign workflow on it.