Huon Wilson

What about a temporary file that's created in the test? (It'll change from run, but that seems fine.)

> Unless you're suggesting a Python-implemented integration test which runs Pants and uses docker_environment? Yeah, that's right. I was under the impression that a normal `RuleRunner`-based integration test would handle...

Ah, I see. That's quite surprising to me so I wasn't thinking along those lines. I'm curious how it'd work with the `pants.core` "backend" that provides the environments functionality.

Hm, okay. I'll register now that I think using the in-repo backends (especially `pants.core`) with an older released orchestrating pants seems like it'd be pretty surprising as a long term...

We've started this at: https://github.com/pantsbuild/example-serverless Thanks @TonySherman for the idea and the initial code.

Here's a fun edge case: I think `*` is technically valid as an env var name, e.g. `env 'ABC_*_GHI=1' env` includes an `ABC_*_GHI=1` line. Thus, supporting glowing here would mean...

The lockfiles are mostly using 23.0.1, and that has a version range of >=3.7,

I've done a search for `-> TestResult` and put in what seem like the relevant files for updating. Please feel free to fix that up.

Heya, just checking in. What's the status of this PR? Is it ready for a re-review or is it waiting on something else?

In https://github.com/pantsbuild/pants/issues/15764, it's discussed that it can be handy to change some values in CI, and that's arguably nicer to do via a `pants.ci.toml` rather than writing having the `BUILD`...