Include go_binary output when running another go_binary

[drone-ah]

Hi,

I have a main go_binary that needs the output from another go_binary module to be included. The module binary is zipped up and uploaded into aws lambda by the main go binary.

I've tried:

main/BUILD

go_binary(
    name="main",
)

go_mod()

go_package(
    name="pulumi",
    dependencies=['path/to/module:lambda']
)

module/BUILD

go_binary(
    name="lambda",
)

go_mod()

go_package(
    name="module_lambda",
)

I've also tried the following targets instead of lambda:

• module_lambda
• module.go:lambda

with no luck. I debugged by outputting all the files in the executable path, but also by using keep-sandboxes" and inspecting the directory afterwards. It only contains the main` binary :(

What am I doing wrong?

[huonw]

Sorry for the trouble!

I'm not sure I understand fully to be able to help, so I'll ask questions instead: is the code in main/ acting as the orchestrator of a deploy, e.g. you do pants run main:main or similar and it executes to run a deploy, using artefacts compiled from other parts of the codebase?

[drone-ah]

Thanks for the reply @huonw and yes - you are correct. pants run main:main should deploy the artefact compiled from the other module.

In other words, I want pants to build a module and pass the output to main so that main can upload the compiled module into aws lambda.

[benjyw]

This doesn't work at the moment, but I have long thought about something like this working. Basically, if anything depends on a packageeable thing, we should package it and ship the resulting package upstream as if it were a source.

[drone-ah]

Ah ok. Thank you for letting me know.

[benjyw]

Could you convert this into an issue, so we can track it? I think this is worth doing

[drone-ah]

I've created the issue now, and will close this discussion :) Thank you :)