Daniel Goldman

a quick workaround is to passthrough your path. In pants.toml: ``` [download-terraform] extra_env_vars = [ "PATH" ] ``` I know it's not ideal.

I think that was fixed with #20241 . Can you try with one of the releases since then (like version 2.18.2rc2)? If not, you should be able to add the...

I think we saw something similar in [this slack thread](https://pantsbuild.slack.com/archives/C046T6T9U/p1707418883408269?thread_ts=1707331262.518309&cid=C046T6T9U). I'm not sure what's happening. We were silencing errors in `init`, and it's possible that an error is being thrown...

we can expose symbols in BUILD files with `def build_file_aliases():` in a `register.py`. I'm not sure if we can invoke rules within that context, though.

Hey, we've solved this issue in mainline now, so I'm going to close this.

I think we said that this wasn't the right approach. In the [slack thread](https://pantsbuild.slack.com/archives/C0D7TNJHL/p1714260455658849) we determined that we'd probably want to just give more/better warnings. The summary of the reasoning...

we could also log those to stdout/stderr, so they're picked up by Docker and visible with, eg, `docker-compose logs -f` There are also a few log streams in the geoserver...

there's always the dumbest possible way of `ln -sf /dev/stdout .../geonode.log`. Although I suspect that there's a better way to configure the logging library of geoserver. there's also `invoke.log`.

> Wow, that's a big PR :) yeah it, uh, got away a bit. Some of it is ansible test code.

Heya, I've merged HEAD into this branch, a rebase was getting messy fast. There are some open mypy problems, most of them seems like Type Tetris related (some pants things...