hey all! just joined :slightly_smiling_face:
Got ...
# helpe
Ekansh Vinaik
05/31/2022, 5:13 PMhey all! just joined 🙂
Got an interesting situation after updating Serverless v2 -> v3 on Seed. Here’s the timeline:
1. updated serverless yml configs to v3 following migration guide
2. deployed to seed, which caused a CloudFormation stack conflict error for 2 of 13 deployments
a. fixed this by deleting the CloudFormation stack and redeploying
b. this seemingly worked fine on our dev deployments
3. did the above steps for production
4. couple bad things happening now:
a. Issues tab no longer shows errors for 1 of those 2 deployments (in spite of there being errors thrown, exactly as they were previously)
b. Resources tab claims that there are no Lambdas deployed in the same API (see attached picture)
we’re wondering how we can bring this back into sync, as we rely on Seed Issues for a quick and dirty overview of issues for our app. if that’s not easy to communicate, I’m wondering how to debug this issue at all? kind of at a loss here
f
Frank
05/31/2022, 10:22 PM
Hey @Ekansh Vinaik, can u give this a try:
• go into your AWS CloudWatch console
• locate the log group
/aws/lambda/webhooks-prod-shopifyWebhookOrdersCreatee
Ekansh Vinaik
05/31/2022, 10:23 PMnope, there are none
f
Frank
05/31/2022, 10:23 PM
hmm.. that’s weird.. let me check something
e
Ekansh Vinaik
05/31/2022, 10:24 PMno prob — seems like there’s an artifact from the previous cloudformation stack
f
Frank
05/31/2022, 10:26 PM
Can you go into the App Settings and try re-enabling Issues again? https://seed.run/docs/issues-and-alerts.html#enabling-issues
e
Ekansh Vinaik
05/31/2022, 10:26 PMthey seem on, want me to disable + re-enable?
f
Frank
05/31/2022, 10:27 PM
Yup, let’s give that a try
e
Ekansh Vinaik
05/31/2022, 10:27 PMon it
Ekansh Vinaik
05/31/2022, 10:32 PMokay, done — still looks like the screenshot w/ webhooks, where nothing is seemingly in the API
f
Frank
05/31/2022, 10:33 PM
Do you see the subscription filters for the log group?
e
Ekansh Vinaik
05/31/2022, 10:33 PMChecking
Ekansh Vinaik
05/31/2022, 10:33 PMah yep
f
Frank
05/31/2022, 10:34 PM
ah nice.. you should start receiving issues for the functions in webhook now
e
Ekansh Vinaik
05/31/2022, 10:34 PMmaybe there’s a slight delay? I can keep an eye on it over the next 10-15min and see if things start rolling in
Ekansh Vinaik
05/31/2022, 10:34 PMawesome thank you so much! anything to worry about re: empty webhooks block?
f
Frank
05/31/2022, 10:35 PM
Routes not showing under the webhook block is likely due to you switched to using the API Gateway HTTP API. And Seed currently doesn’t support display routes for HTTP APIs in the resources tab (on our roadmap).
Frank
05/31/2022, 10:36 PM
But if you scroll down the webhooks service on the resources tab, select
View Resourcese
Ekansh Vinaik
05/31/2022, 10:36 PMGot it — what’s the alternative (if not the HTTP API)? I’m happy to switch back (unless it truly doesn’t matter)
Ekansh Vinaik
05/31/2022, 10:37 PMyup, found those there. good to know those are the same! ID matched but mismatch in the view was a little confusing
f
Frank
05/31/2022, 10:39 PM
HTTP API is newer and recommended. The APIs are shown at the top of the resources page, and the services are shown at the bottom. The only thing affected right now is that the routes are not being displayed on the resources page up top, everything else works as normal. Not affected in any way.
e
Ekansh Vinaik
05/31/2022, 10:39 PMAwesome — thanks for your help + speedy response! It’s very appreciated, and that was deceptively simple
f
Frank
05/31/2022, 10:39 PM
Definitely keep it this way, as it’s something we are going to support.
Frank
05/31/2022, 10:40 PM
👍