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
There shouldn't be a back tick in the code section for Kubernetes
kubectl logs deployment/queue-worker -n openfaas``
There is a backtick at the end of
kubectl logs deployment/queue-worker -n openfaas`
Remove backtick
I didn't even try to run the command with the backtick, so I'm not sure if it even throws an error.
FaaS-CLI version ( Full output from: faas-cli version ): n/a
faas-cli version
Docker version ( Full output from: docker version ): n/a
docker version
Are you using Docker Swarm (FaaS-swarm ) or Kubernetes (FaaS-netes)? n/a
Operating System and version (e.g. Linux, Windows, MacOS): MacOS Catalina
Link to your project or a code example to reproduce issue: see above
The text was updated successfully, but these errors were encountered:
Please feel free to send a pull request for this. Make sure that the commit is signed off so that the automation doesn't reject it 👍
Sorry, something went wrong.
No branches or pull requests
Expected Behaviour
There shouldn't be a back tick in the code section for Kubernetes
Current Behaviour
There is a backtick at the end of
Possible Solution
Remove backtick
Steps to Reproduce (for bugs)
Context
I didn't even try to run the command with the backtick, so I'm not sure if it even throws an error.
Your Environment
FaaS-CLI version ( Full output from:
faas-cli version
): n/aDocker version ( Full output from:
docker version
): n/aAre you using Docker Swarm (FaaS-swarm ) or Kubernetes (FaaS-netes)? n/a
Operating System and version (e.g. Linux, Windows, MacOS): MacOS Catalina
Link to your project or a code example to reproduce issue: see above
The text was updated successfully, but these errors were encountered: