Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

(by default, and I've turned it on explicitly just to be sure)

I'm not sure if there is an easier way to do this (a more scoped json), but can you sanity check with something like: `./pants help-all | jq '.scope_to_help_info[""].advanced | .[] | select(.config_key=="pantsd")'`

If I run that command vs the  `./pants --pantsd ...`  version of that command vs the `./pants --no-pantsd ...` version of that command I get 3 different `value_history` and all are what you'd expect.

For example:
```$ PANTS_PANTSD=False ./pants help-all | jq '.scope_to_help_info[""].advanced[] | select(.config_key=="pantsd") | .value_history'
{
  "ranked_values": [
    {
      "details": null,
      "rank": "NONE",
      "value": null
    },
    {
      "details": null,
      "rank": "HARDCODED",
      "value": true
    },
    {
      "details": "from env var PANTS_PANTSD",
      "rank": "ENVIRONMENT",
      "value": false
    }
  ]
}```


Ugh, figured it out. Operator error. I was using a `pants_from_sources` script which also turns off pantsd (for ~reasonable reasons, but not in my case...)