-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use CfnParameter valueAsNumber in SQS Queue #7126
Comments
@shivlaks what is the right way to do this? |
Interesting! I think |
@eladb it only seems to fail only with SQS. It seems to work fine with other resources such as Lambda. |
@amwill04 I think it works for Lambda because of an oversight where the i.e. the range for const handler = new lambda.Function(stack, 'handler', {
handler: 'index.handler',
code: lambda.Code.fromInline('boom'),
runtime: lambda.Runtime.NODEJS_10_X,
timeout: 901
}); SQS on the other hand validates the props that are set (which contain a token) and it's erroring out there |
@shivlaks does that mean with the way |
validation that was being performed was not taking into account that tokens could be provided for these parameters. added a check and some tests to allow parameters to be supplied. Fixes #7126
… properties validation that was being performed was not taking into account that tokens could be provided for these parameters. added a check and some tests to allow parameters to be supplied. Fixes #7126
… properties (#8252) validation that was being performed was not taking into account that tokens could be provided for these parameters. added a check and some tests to allow parameters to be supplied. Fixes #7126 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
If trying to use a
CfnParameter
with aSQS
Queue
you end up with the following error:Reproduction Steps
Error Log
Environment
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: