Was there a specific design decision about using

environments-preview.names

?

pex_binary(
  name="main",
  dependencies=[":lib"],
  environment="//:docker_denv",
)

As in, is there an explicit reason why I can't use the standards Pants convention

//:

or

:

to tell the target where to grab the associated environment? Didn't see anything in the tracking ticket about it: https://github.com/pantsbuild/pants/issues/17355 Not a huge deal one way or the other, but it was a bit of a surprise

I believe the goal is to allow remapping an environment's "name" to a different actual environment target via local configuration (e.g.,

.pants.rc

etc.)

I believe the goal is to allow remapping an environment's "name" to a different actual environment target via local configuration

Ahhh, that's interesting.

Also I wonder if we should rename

environments-preview

to just

environments

Do we think it is stable enough?

The Rust-side support for environments is already in use even when the default local environment is the only thing used.