-
Notifications
You must be signed in to change notification settings - Fork 7
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
fix: consumerTable.get returns customer #435
Conversation
View stack outputs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is good to merge, but if you could swap out the exponential retry function for p-retry
it'd be even good-er to merge.
Context
While testing the Egress Tracking System in Staging, an error occurred indicating that the router couldn't resolve the customer:
Issue
The error arises because the
consumerTable.get
query does not include thecustomer
field in its projection, despite the customer existing inconsumerTable
and being manually retrievable.Fix
This PR updates the
consumerTable.get
query to ensure thecustomer
field is projected correctly, allowing the router to resolve the customer as expected. It also fixes the related tests to reflect this change accurately.