[Enhancement] Support different output formats (e.g. JSON)

[akittana]

Is your feature request related to a problem? Please describe.
Currently, it is hard to parse the output of cloudformation-guard using other scripts since the output is in text only, having different output formats would help ingest that output to different tools.

Describe the solution you'd like
It will be nice to have an option like cfn-lint/cfn_nag/cfripper/tflint/tfsec/terrascan/checkov that allows the user to specify different output options

Describe alternatives you've considered
Current solution is to parse the text output which is not ideal

[nathanataws]

This shouldn't be too hard to pull together. I can just use serde logic that's in the lambda to give you the same structured result from the CLI.

[PatMyron]

This would be useful for IDE/editor/code review bot integrations. Should consider existing formats to decrease unique integration work

[sfarazkazmi]

+1 on this. Text parsing is not ideal and we need JSON based output.

[johnttompkins]

As mentioned in #111, rule evaluation output in the form of JSON is targeted for the next release

[tvb]

@jotompki does this mean it will clear the road for #93 ?

[0xjjoyy]

Is junitxml output so we can integrate with CodeBuild reports also on the roadmap?

[dchakrav-github]

Current set of output-formats supported as a part of PR #156. Supports JSON, YAML and SingleLine formats. Does not have XML or other representation support. Contributions welcome post PR merge :)

[gandhek]

We have released a new minor version of Guard 2.0 which supports various output formats that @dchakrav-github mentioned. You can find the newest version at - https://github.com/aws-cloudformation/cloudformation-guard/releases/tag/2.0.3