This repository has been archived by the owner on Oct 21, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 9
Add-ConIf cannot be used as a value for a parameter #82
Labels
Comments
How's this look @indented-automation ? |
scrthq
added a commit
that referenced
this issue
Jul 31, 2020
## 2.13.0 - 2020-07-30 * [Issue #81](#81) * Fixed: `Add-ConIf` parameter error message * Fixed: `Add-ConIf` now allows boolean values * [Issue #82](#82) * Fixed: Condition Functions are now supported on any parameter that already accepts Intrinsic Functions * Miscellaneous * Updated PseudoParameter list to current spec.
scrthq
added a commit
that referenced
this issue
Jul 31, 2020
## 2.13.0 - 2020-07-30 * [Issue #81](#81) * Fixed: `Add-ConIf` parameter error message. * Fixed: `Add-ConIf` now allows boolean values. * [Issue #82](#82) * Fixed: Condition Functions are now supported on any parameter that already accepts Intrinsic Functions. * Miscellaneous * Updated PseudoParameter list to current spec. * Switched default branch from `master`
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
JSON and YAML templates imply that is should be possible to use an If condition as the value for a parameter. However, this fails parameter validation.
Steps to reproduce
Expected result
Should allow a template to be generated containing the following content:
Actual result
An error is raised:
Related to #81 for handling of bool values in ValueIfTrue and ValueIfFalse.
The text was updated successfully, but these errors were encountered: