For historical reasons, Sceptre has never validated Stack config parameters that are passed in to CloudFormation stack parameters. Blocks that contain bools, ints etc give rise to confusing failures. For example:
parameters:
someBool: true
Would lead to an error appearing like:
"Parameter validation failed:\nInvalid type for parameter Parameters[0].ParameterValue, value: 1, type: <class 'bool'>, valid types: <class 'str'>"
In more complicated examples it is often quite unclear what Parameter[0] means.
A feature here is added at the time of Stack instantiation to perform validation of the input stack parameters in a similar manner to how the ignore and obsolete settings were already being checked.
PR Checklist
[x] Wrote a good commit message & description [see guide below].
[x] Commit message starts with [Resolve #issue-number].
For historical reasons, Sceptre has never validated Stack config parameters that are passed in to CloudFormation stack parameters. Blocks that contain bools, ints etc give rise to confusing failures. For example:
Would lead to an error appearing like:
In more complicated examples it is often quite unclear what Parameter[0] means.
A feature here is added at the time of Stack instantiation to perform validation of the input stack parameters in a similar manner to how the ignore and obsolete settings were already being checked.
PR Checklist
[Resolve #issue-number].poetry run tox) are passing.poetry run pre-commit run --all-files).Approver/Reviewer Checklist
Other Information
Guide to writing a good commit