Richard Gee

Unfortunately I think you may have been overtaken by events with this one. The issue is now over two years old and the 0.9.0 work seems to have been undertaken...

I'm not sure this is as simple as it seems on first glance owing to the decision to support the use case in #478. Consider a scenario where the handler...

Up to you. I think the original sentiment is still valid - the user is misdirected towards an error situation through what is essentially an informational failure. A silent failure...

Probably worth catching up with some of the discussion on #373 too.

``` $ faas context create staging --gateway https://staging.openfaas.com` Context 'staging' created using gateway: https://staging.openfaas.com ``` ``` $ faas context set staging Setting gateway: https://staging.openfaas.com ``` ``` $ faas context get...

I considered `use` too, seems more intuitive. However, it gave me a sense of single use whereas `set` gives the user a sense of persistence. I like the idea of...

I like the idea of utilising the root command of `context`. Take the point on `show`; I think we've used `list` elsewhere.

I'll always advocate consistency between the YAML and the CLI - for example `build_options` and `build-options` drive me crazy. I'm torn here because `--cpu-limit` is more idiomatic but the YAML...

My thoughts are that the behaviour needs to be deterministic. At the moment, if the backend is missing a secret, the same stack file containing a function referring to the...

As I understand the issue: A stack file has 100 functions detailed. 50 of them have a unique secret specified. The remaining 50 have no secret. One of the secrets...