I am using

experimental_run_shell_command

or

experimental_shell_command

to run a custom command to output a file. is there a way to a. have

experimental_run_shell_command

generate a "file() that I can have placed in the dist folder ? and have Pants know about it ? or b. have

experimental_shell_command

place the file in the "dist" folder and be preserved - currently I am using a "archive" to grab the file from the process Context - I am trying to debug the actual tool. and I am struggling to work out how to 1. run

experimental_run_shell_command

or

experimental_shell_command

and debug, and keep the file it produces. The "file" is the final output of a "package" process (that is my desired outcome)

experimental_shell_command

uses Pants's code generation mechanism. So files it creates are placed in the sandbox of downstream processes that need source files

that us helpful @happy-kitchen-89482 - i sturrgled to work out how to get to the output . was very complicated. this would have been good to be documented somewhere does

Pants

have something similar to

Please

's style of

plz build //path/to:target --shell

There is the

--no-process-cleanup

flag, that preserves the sandbox directories (and logs their paths) so you can inspect them