#petersaverman
slim lagoon
jolly path
hi, was there a specific part you were running into difficulty with?
stray saddle
I'm getting prices for two or our products. I have two archived and two active on each product. When running it locally this works and I get the two prices for both products. When deployed to a Lambda I get the two new prices for one product and then all of them (archived and new) for the second one.
Same API key in both places
jolly path
do you have the request ID req_xxx for the two respective GET requests?
stray saddle
Oh, not sure how to get those.
jolly path
https://dashboard.stripe.com/logs and filter by Method=GET , /v1/prices, the timestamps, etc
stray saddle
Gotcha. Hold on!
jolly path
you can also log them https://stripe.com/docs/api/request_ids?lang=python
jolly path
Gotcha. Hold on!
note that my shift ends in about 10 minutes and then we're going to close the server until tomorrow(US holiday today), just to be upfront! So you might want to write to https://support.stripe.com/?contact=true too
stray saddle
Ok, I will
The one that works is here req_pcE6B2o1icCgnz and the one that gets the archived once is probably this one (based on the IP) req_1pbd1SdNcg6d5l
Then again, they look like they don't have the simliar package version but I specifically say in the requirements that it should be.
jolly path
yeah they're definitely not the same package, and the parameters themselves are different, which implies to me that the actual code in your business logic must be different
so I don't think it could be "exact same piece of code locally and in an AWS Lambda", the deployment must not be what you think it is
stray saddle
Yes, looks like it. I then wonder why it doesn't update the Lambda... I need to check this out. Thank you for pointing to the logs. That will help a lot!