[WIP] Use multi-stage build for CSharp

[rorpage]

Signed-off-by: Robbie Page rob@rorpage.com

Description

I have updated the csharp template to use multi-stage. The first stage is using the dotnet SDK, and the second uses the runtime.

Motivation and Context

The dotnet images are rather large so by implementing a multi-stage build, we decrease the end function image.

• I have raised an issue to propose this change (required)
  #53

How Has This Been Tested?

I updated my template locally, created a new csharp function, built, deployed, and invoked the function and saw that everything ran as expected.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have signed-off my commits with git commit -s
• I have added tests to cover my changes.
• All new and existing tests passed.

[alexellis]

Thanks for this. Can you try this with a new image name including pushing to the hub?

[alexellis]

@rorpage did you say this is working now?

[alexellis]

I got:

exit status 145
Did you mean to run dotnet SDK commands? Please install dotnet SDK from: 
  http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409

Right - I remember the issue. Please change the hard-coded fprocess in the Golang code with this PR. It'll fix everything.

Change it here:

https://github.com/alexellis/faas-cli/blob/a95a2809593fff93b07f44684ffc490ba4536c74/proxy/deploy.go#L31

[rorpage]

@alexellis This has been tested locally with the deploy.go fix and am no longer getting the exit status message.

[alexellis]

Good work :-) this will make a difference for people