We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add namespace field to the stack.yml schema
I'd like to write this:
functions: webhook: namespace: staging-fn
Then run faas-cli deploy, and have the function deployed into the staging-fn namespace.
faas-cli deploy
staging-fn
Functions can now be deployed into a custom namespace via faas-cli deploy --namespace, but not with a YAML file.
faas-cli deploy --namespace
Extend the structs / schema.
Some of the deployment paths are already up to date from when we added --namespace in #693 so this shouldn't need wide-spread changes.
--namespace
This work is part of: openfaas/faas-netes#511
The text was updated successfully, but these errors were encountered:
This appears to be done already, a user reported that it wasn't available, but I've tested e2e with the latest faas-cli and it worked fine.
Sorry, something went wrong.
No branches or pull requests
Add namespace field to the stack.yml schema
Expected Behaviour
I'd like to write this:
Then run
faas-cli deploy
, and have the function deployed into thestaging-fn
namespace.Current Behaviour
Functions can now be deployed into a custom namespace via
faas-cli deploy --namespace
, but not with a YAML file.Possible Solution
Extend the structs / schema.
Some of the deployment paths are already up to date from when we added
--namespace
in #693 so this shouldn't need wide-spread changes.This work is part of: openfaas/faas-netes#511
The text was updated successfully, but these errors were encountered: