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

Pants

Hello, what would it take for us to be able to source the tag for a docker image from a file, as opposed to a string/env var that we refer to in the BUILD file? (Thinking of something similar to the <https://github.com/bazel-contrib/rules_oci/blob/main/docs/push.md#oci_push_rule-remote_tags|remote_tags> feature of rules_oci in the bazel world)

Would be happy to make this contribution if it's something maintainers are willing to entertain

Going to get started by trying out a custom plugin: <https://www.pantsbuild.org/stable/docs/docker/tagging-docker-images#providing-additional-image-tags-with-a-plugin>, but this seems like a reasonable thing to first-class in `docker_image`

Haven't tried this myself, but you ought to be able to just add this to a <https://www.pantsbuild.org/stable/docs/using-pants/key-concepts/options#pantsbootstrap-file|.pants.bootstrap> file.

(ie. as a setup step, read the file and set the env variables that you want. Then your `docker_image` target can expect env vars.)

Hm, that'd work - but was explicitly hoping to depend on something like the output of `vcs_version` to provide the image tag (for consistency between images &amp; other published artifacts like wheels)