https://pantsbuild.org/ logo
#development
Title
# development
h

happy-kitchen-89482

11/17/2020, 3:24 AM
(by default, and I've turned it on explicitly just to be sure)
e

enough-analyst-54434

11/17/2020, 3:50 AM
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:
Copy code
$ 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
    }
  ]
}
h

happy-kitchen-89482

11/17/2020, 4:38 PM
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...)
Thanks!