36489f3a55
* chore: bump faas-js-runtime and cloudevents for node & TS The Node.js and TypeScript templates have been bumped to the latest versions of faas-js-runtime (2.2.2) and CloudEvents (7.0.1). There is an issue with the `expectType` test for TypeScript CloudEvent functions which I can't quite figure out, but the type test is not critical and does not do anything to validate other than whether the function signature is what's expected by faas-js-runtime, and in this case, I think type exported type for faas-js-runtime may actually be the issue here. Signed-off-by: Lance Ball <lball@redhat.com> * chore: pin all github actions to go 1.20.2 There was a change in how go parses URLs in versions higher than 1.20.2 (likely 1.20.6 and up) which breaks the Docker API's handling of daemon URIs. This fix pins the Go version at a version known to work with the existing Docker API and `func` implementation. Signed-off-by: Lance Ball <lball@redhat.com> --------- Signed-off-by: Lance Ball <lball@redhat.com> |
||
|---|---|---|
| .. | ||
| certs | ||
| go | ||
| node | ||
| python | ||
| quarkus | ||
| rust | ||
| springboot | ||
| typescript | ||
| README.md | ||
| manifest.yaml | ||
README.md
Templates
Contains all example source code, scaffolding, certificates and metadata used by func when creating and building function instances.
To rebuild run make templates (which caches). To force a full rebuild run
make clean && make
Layout
Each directory within templates corresponds to a known language runtime.
The certs directory is a reserved word containing root SSL certificates.
Each directory within a runtime directory corresponds to a named templaate.
The scaffolding directory within the runtime directory is a reserved word
containing the adapter code that converts a function with a given method
signature into a service by way of the external function runtime libraries.
Packaging
When updates are made to these templates, they must be packaged (serialized as
a Go byte array) by running make templates (which rebuilds
generate/zz_filesystem_generated.go, and checking in the resultant
./generate/zz_filesystem_generated.go file.
How it works
The ./generate/templates directory contains Go program that generates ./generate/zz_filesystem_generated.go.
The file defines byte array variable named TemplatesZip.
The variable contains ZIP representation of the templates directory.
The byte array variable is then used to instantiate exported global variable function.EmbeddedTemplatesFS,
which implements standard Go interfaces fs.ReadDirFS and fs.StatFS.
Rationale
Until such time as embedding static assets in binaries is included in the
base go build functionality (see https://github.com/golang/go/issues/35950)
we need to use our custom serialization script (./generate/templates/main.go).
Native Go embedding introduced in Go 1.16 could be used for executable binary, however it cannot be used for library. For a library we need to generate a Go source code containing the templates.