Open hauntingEcho opened 2 years ago
Also applies to AWS::StackName
@hauntingEcho Although unsure, you might be affected by the issue https://github.com/aws/aws-extensions-for-dotnet-cli/issues/116. If yes, please close this a duplicate.
My understanding is that 116 only affects the --template-substitutions
command-line parameter, which I am not using. This issue is when using CloudFormation's pseudo-parameters
Describe the bug
if you use
!Ref AWS::NoValue
as a possible result of an!If
, thendotnet lambda package-ci
will fail.Expected Behavior
template provided in the reproduction steps works with
dotnet lambda package-ci
Current Behavior
while
aws cloudformation validate-template
accepts the file,dotnet lambda package-ci
fails with the error:Reproduction Steps
Using
serverless.yaml
:and
aws-lambda-tools-defaults.json
:call
dotnet lambda package-ci -sb ${bucket}
(using a${bucket}
that you can write to)Possible Solution
Temporary workaround: adding quotes around "AWS::NoValue" makes the utility accept it.
Additional Information/Context
No response
Targeted .NET platform
6
CLI extension version
5.1.4
Environment details (OS name and version, etc.)
Windows 10