Skip to content
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(db): targets:upsert to properly handle errors #13584

Merged
merged 1 commit into from
Sep 17, 2024
Merged

Conversation

bungle
Copy link
Member

@bungle bungle commented Aug 27, 2024

Summary

kong.db.targets:upsert was not handling errors with kong.db.targets:each_for_upstream correctly. This fixes it.

### Summary

`kong.db.targets:upsert` was not handling errors with `kong.db.targets:each_for_upstream`
correctly. This fixes it.

Signed-off-by: Aapo Talvensaari <[email protected]>
@chronolaw
Copy link
Contributor

Should we add a change log entry?

@bungle
Copy link
Member Author

bungle commented Sep 2, 2024

Should we add a change log entry?

@chronolaw please suggest what to write there? In general I don't feel this of any value to our users (the changelog describing this - nobody has probably ever hit to this).

Copy link
Contributor

@nowNick nowNick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it linked to this: #12987 ?

@bungle bungle merged commit 71e7cb6 into master Sep 17, 2024
40 checks passed
@bungle bungle deleted the fix/db-each-err branch September 17, 2024 20:24
@team-gateway-bot
Copy link
Collaborator

Successfully created cherry-pick PR for master:

curiositycasualty pushed a commit that referenced this pull request Oct 15, 2024
### Summary

`kong.db.targets:upsert` was not handling errors with `kong.db.targets:each_for_upstream`
correctly. This fixes it.

Signed-off-by: Aapo Talvensaari <[email protected]>
(cherry picked from commit 71e7cb6)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants