-
Notifications
You must be signed in to change notification settings - Fork 35
dataSources / tableName as Ref not processed / InvalidParameterType: Expected params.TableName to be a string #20
Comments
See #17
Currently, we do not support CloudFormation syntax. Now that you are the second person to ask for it, we will look at implementing sooner. 😄 |
We're having this issue also, any news on the possibility of this? Would be really helpful :) @cbaron |
Personally, I do not have time to do this in the coming weeks. I will reach out to some collaborators and/or try to carve out some time if this is what the people want! Thanks for the feedback. As always, anyone here is welcome to put up a PR 😄 |
It's great to hear that people are using the emulator and have a need . I am not sure when we can get to this but we intend to put it on the roadmap now. |
I started on this... One thing that came to mind is if that syntax works in serverless (not emulated) I have vague recollection of ref's not getting resolved outside of the |
@EwanValentine I will have a alpha release out once I manage to get my otp code :) |
Okay, I released an alpha version |
Wow! Amazing work! 🔥I'll give it a test and let you know my findings, thanks for looking into this!! |
Using a "Ref: " for tableName is not supported
Error:
There is no problem if
{ Ref: UsersTable }
is replaced with a string - e.g. "appnam-users-table"The text was updated successfully, but these errors were encountered: