Implement machine readable output format about serverless-toolkit HOT 2 OPEN

This is definitely on the roadmap for post SIGNAL. Thanks for filing this.

from serverless-toolkit.

OK, so I've been working on this and I got quite a way into it before getting confused 😄

The commands list, list-templates, deploy, activate and logs all call off to APIs and have JSON results.

The commands new and start do not do that and don't really have an obvious return data. start isn't really a command that would be used by a machine but new is used by create-twilio-function.

So far, the work is ongoing on my json-output branch. I've added a output-format option to the BaseCliFlags but now I realise that the start and new commands don't necessarily need a JSON output, so perhaps it shouldn't be in BaseCliFlags.

So, to my questions:

Should the start and new commands have the --output-format flag as an option at all?

Should those two have another flag/option which silences their output so that other programs can use them without them making a mess over the terminal (e.g. see the test output of create-twilio-function)?

Or should I just leave the start and new commands alone for now?

from serverless-toolkit.