Specify the Path of the Golang Executable #755
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #754
I enhanced
GolangAppHostingExtension
to define a new override ofAddGolangApp
that allows specifying the path of the Golang executable relative to the working directory. This is useful for scenarios where the Golang executable is in acmd
subdirectory, but the working directory needs to be the root of the project for accessing resources relative to the working directory at runtime. It is also useful when there are more than one executable in a Go module.I updated the existing
AddGolangApp
method to call the new overload passing.
as the executable path. This will support existing consumers without breaking their integrations.PR Checklist
Other information