faas-cli icon indicating copy to clipboard operation
faas-cli copied to clipboard

Official CLI for OpenFaaS

Results 82 faas-cli issues
Sort by recently updated
recently updated
newest added

If I want to apply a memory limit, or CPU limit I would need to create YAML file and deploy my function. ## Expected Behaviour I would like to directly...

Feature: Support OAuth2/OIDC and Bearer token ## Expected Behaviour As a user with a custom OAuth2/OIDC *OpenFaaS authentication plugin* configured on my gateway, I need to be able to "log...

help wanted
skill/intermediate
priority/high
design/review
size/l

**Support for OpenID based authentication** **why open id ?** 1. enterprise standard to support variety of user flows. 2. connect various to various identity broker like github, ldap 3. All...

## Expected Behaviour Add new 0.6 Knative Serving spec to generate command ## Current Behaviour Compatible with the Alpha variant. ## Possible Solution Copy/paste code to output new format when...

## Expected Behaviour The following should generate a Rancher Rio Service definition: ```sh faas-cli generate --api=services.rio.cattle.io ``` ```yaml apiVersion: rio.cattle.io/v1 kind: Service metadata: name: figlet namespace: default spec: concurrency: 10...

help wanted
size/xs
good first issue

During provider development i've found it helpful to log the the entire request/response sent from the CLI to the gateway. ## Expected Behaviour `faas cli deploy --debug` ## Current behaviour...

enhancement
design/review

Currently, the base images used for creating and deploying functions are not validated for trust-worthiness during the function build process. However, enterprises are very security and compliance centric and hence...

TLS warning messages should be refactored to a more flexible approach ## Expected Behaviour something like ``` checkTLS(io.Writer, gateway, tlsenabled) ``` should validate and print the warning ## Current Behaviour...

design/review
priority/low

## Expected Behaviour It would be nice/better if the CLI flag values were scoped to the methods being run instead of the package, e.g. we shouldn't expose the `secretName` variable...

`deploy` and `store deploy` have `--update` and `--replace` flags, which should be strictly exclusive to ensure consistency of these flags ## Current Behaviour Valid ``` --update=false --replace=true --update=true --replace=false --update=false...

proposal
design/review