Programmatic outputs

[alytle]

Hey folks,

Have you put any thought into supporting a machine readable output format (like aws cli --output json, etc) for the purposes of automation? I know this tool was created for humans to directly manage stacks, but I've got a few projects where we've got large cfn-cli config files, and we're exploring whether we could switch to a CI/CD approach through CodePipeline, Build, etc. To do any sort of automated deployments, we would need to be able to parse the outputs.

Thoughts?

[GlieseRay]

It could be supported I think. @alytle Do you have any detail workflow or example use case that we could take look ?

cc: @Kotaimen

[alytle]

Not yet, I'm mostly just checking in first before I put any time into it. My thinking is that if we want tooling to run cfn-cli, we would want said tooling to be able to parse the result of any given command. I'm thinking that we could probably suppress the real-time CFN Event logging in this case, as there is no human watching the output. Instead, we would just output a standard "result" JSON object for any commands which could then be parsed for success/failure.