Redis client is hanging deployment? #78
Unanswered
thecodekitchen
asked this question in
Q&A
Replies: 2 comments
-
Forgot to mention, I ran 'npm install redis' from ./commands_layer/nodejs in order to install the Redis dependency. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi, A general debugging tip: Try to start with the hello command and only make small increments that you deploy and test. This makes it easier to find issues. The CreateCommandsInvoker can indeed hang if errors occur in CreateCommandsFunction. If you have any ideas for a better solution, feel free to suggest them! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm attempting a very basic Redis integration in the file getBeastCommand.js. I replaced the original helloCommand.js file with it. The original hello deployment worked great, but when I changed the file to this and renamed it, the deployment hung on the step where it creates the 'Custom:CreateCommandsInvoker' resource, pictured here:
When I abort, it leaves me with an incomplete set of resources that interfere with further deployments, so I have to keep deleting them manually in all the different AWS services in order to try again, but it keeps failing at the same step. What am I doing wrong here?
Beta Was this translation helpful? Give feedback.
All reactions