Chuck Meyer

Speaking to the internal team, they decided not pursue this for the reasons @kddejong outlined above.

Agreed. This would be a good business logic addition to compare values. I'll label this as an enhancement.

I would love to see the `cloudformation package` command extended to handle includes -- that way you could have local file paths in your template that we could evaluate pre-deploy...

Can you share your .cfnlintrc? Here is ours, which works: ``` templates: - templates/**/*.yaml - templates/*.yaml append_rules: - append_rules ignore_templates: - templates/app/env/*/app_env.yaml - templates/app/env/*/rpc_env.yaml ```

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...

Thanks for the feedback. Could be something we could do with a value check here. We're slowly trying to enrich the spec with value data, but we're doing it service...