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.
Signed-off-by: Alex Ellis (OpenFaaS Ltd) [email protected]
Description
Fix vendoring for golang-http by reverting to method prior to workspaces
How Has This Been Tested?
Tested with a private Go module which was vendored, setting GO111MODULE: off in build_args in stack.yml
I also created a nested package called pkg and referenced it as "handler/function/pkg" from handler.go which worked as expected.
Closes: #78
How are existing users impacted? What migration steps/scripts do we need?
Imports remained the same, but we will need to check docs and blog posts
https://www.openfaas.com/blog/golang-deep-dive/
https://github.com/openfaas/golang-http-template#20-golang-http
Checklist:
I have:
git commit -s
For the privately vendor code:
For using Go modules w/o any vendoring:
The stack.yml file was unchanged.