cfn-include
cfn-include copied to clipboard
Put `Fn::Eval` behind CLI switch
I would want cfn-include to remain clear of eval unless explicitly enabled through a CLI switch. A template could contain malicious code in the eval block and we would happily execute it. Instead, I'd suggest we would fail the Fn::Eval block and ask the user to pass a --eval switch to the CLI to enabled it. @nmccready what are your thoughts? Any other risky functions you can think of?
Fine with me I believe that’s the only one.
This also includes Fn::IfEval as well
Done https://github.com/monken/cfn-include/pull/63