A question was asked if we should be including template issues and best practices with the same repository of rules.
Example would be for an image ID property.
Another example would be if you are specifying a password for a RDS database we make sure the REF to a parameter has the property NoEcho True set. Again a best practice but not a requirement for the template to work.
This is a great question and deserves some conversation. I see two options.
Right now I'm leaning towards a model in which we keep the rules in this repo but allow people to disable best practices.
I like the "Error" vs. "Warning" model similar to other linters (Flake8 for example). This would allow separation of issues that will cause CloudFormation to fail from stylistic or other best practices.
So I think we are in agreement of this.
Pull request 28 includes a capability to disable all Warnings.
Re-opening this issue to track progress on some broadly applicable best practices:
related: https://github.com/aws-cloudformation/cloudformation-guard/pull/21/