I noticed that the `export-codegen` goal is part o...
# general
b
I noticed that the
export-codegen
goal is part of the
pants.backend.docker
backend, but... I can't think of why it would need to be associated with docker. Am I missing something? https://www.pantsbuild.org/docs/reference-export-codegen
c
It’s for when you have
docker_image(instructions=["FROM ..", "COPY ..", …])
those inline instruction gets “code generated” into the
Dockerfile
b
Ah I see, but I think that goal works for other things, like protobuf codegen and
experimental_shell_command
too?
c
yep
h
I'm hoping it will go away soon, with the functionality folded in to the
export
goal
👍 1
b
It's thus a bit strange that goal only exists after activating docker, even though it's useful elsewhere too
c
but you shouldn’t be getting the protobuf stuff, only the “core” codegen bits, I belive..
there are other backends that give you that as well, not only docker..
b
Ah, so maybe it's a bug in the shell backend that it supports
export-codegen
for
experimental_shell_command
but doesn't enable that goal?
c
yea, so could it be
b
Thanks for talking through it. Docs issue: https://github.com/pantsbuild/pants/issues/17772 PR to fix some backends: https://github.com/pantsbuild/pants/pull/17773