You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I enhanced GolangAppHostingExtension to define a new override of
AddGolangApp 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 a `cmd` 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 Golang executable in a Go module.
Resolves#754
Co-authored-by: Tommaso Stocchi <tstocchi@microsoft.com>
/// Adds a Golang application to the application model. Executes the executable Golang app.
37
+
/// </summary>
38
+
/// <param name="builder">The <see cref="IDistributedApplicationBuilder"/> to add the resource to.</param>
39
+
/// <param name="name">The name of the resource.</param>
40
+
/// <param name="workingDirectory">The working directory to use for the command. If null, the working directory of the current process is used.</param>
41
+
/// <param name="executable">The path to the Golang package directory or source file to be executed. Use "." to execute the program in the current directory. For example, "./cmd/server".</param>
42
+
/// <param name="args">The optinal arguments to be passed to the executable when it is started.</param>
43
+
/// <param name="buildTags">The optional build tags to be used when building the Golang application.</param>
44
+
/// <returns>A reference to the <see cref="IResourceBuilder{T}"/>.</returns>
0 commit comments