How are you supposed to deal with duplicate names?

[rdeusser]

I may have missed something in the documentation somewhere, but how are duplicate names supposed to work? What I mean is, if I have a project that looks like this:

test
├── BUILD
├── Dockerfile
├── go.mod
└── main.go

pants tailor :: generates the BUILD file to look like this:

go_binary(
    name="bin",
)

docker_image(
    name="docker",
)

go_mod()

go_package(
    name="test0",
)

If I run pants package test it builds a Docker image with a name of docker. I could just rename it to test, but that won't work because go_mod() has a default name of test and I also want the binary to have a name of test. If I copy the test target as is in the Dockerfile to /usr/local/bin, the binary ends up as /usr/local/bin/test/bin which is kind of weird. Playing hot potato with names isn't ideal, but I'm not sure if there is a better way.

[kaos]

Hi,

Assuming you've seen https://www.pantsbuild.org/docs/targets#target-addresses

The name is to address that particular target only, and may be used by default by targets such as docker_image to produce the image name, but there are dedicated fields to customize the various parts that make up the final image name or binary output filename. See https://www.pantsbuild.org/docs/tagging-docker-images#setting-a-repository-name about how to tag docker images. There's a lot of flexibility to support many different use cases.

To change the name of your go_binary there is a output_path field if you don't want it to base it on the target name: https://www.pantsbuild.org/docs/reference-go_binary#codeoutput_pathcode

[rdeusser]

I had a feeling I missed something in the docs. Thanks @kaos!