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
Implements a user-experience changes:
faas-cli new - when the templates folder is not present the
language will be looked up in the template store using the
default URL or an overriden one.
faas-cli publish - when no template folder is available then
a pull will be carried out if a configuration section is
present with a template given within in
Filtering - whilst there is no way to avoid pulling all the
templates wihtin a repository, only the requested/needed ones
are expanded by commands like faas-cli new.
Tested mainly with existing-unit tests, faas-cli new / publish
with and without a templates folder.
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
> Note: You can set your own custom store location with `--url` flag or set `OPENFAAS_TEMPLATE_STORE_URL` environmental variable
218
218
219
-
To pull templates from the store just write the name of the template you want `faas-cli template store pull go` or the repository and name `faas-cli template store pull openfaas/go`
219
+
To pull templates from the store just write the name of the template you want `faas-cli template store pull golang-middleware` or the repository and name `faas-cli template store pull openfaas/golang-middleware`
220
220
221
-
To get more detail on a template just use the `template store describe` command and pick a template of your choice, example with `go` would look like this `faas-cli template store describe go`
221
+
To get more detail on a template just use the `template store describe` command and pick a template of your choice, example with `go` would look like this `faas-cli template store describe golang-middleware`
222
222
223
223
> Note: This feature is still in experimental stage and in the future the CLI verbs might be changed
0 commit comments