-
-
Notifications
You must be signed in to change notification settings - Fork 609
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
test: Add ProxySQL to our Docker development stack #6754
Conversation
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.
(sniping first review because @jsha is focused on rustls stuff this week) LGTM with one nit
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.
Do we want to connect to proxysql in the integration tests to check arbitrary database output?
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.
@pgporada said:
Do we want to connect to proxysql in the integration tests to check arbitrary database output?
This suggestion makes sense to me. Phil has now approved without this comment being visibly addressed -- was it discussed offline yesterday? What was the conclusion of that discussion?
We didn't discuss it, but changes were pushed based on my other comments. I took the lack of that change as, "No I don't think it's necessary" and approved it anyways. |
Oh, I must have missed this comment. Yeah I can totally make the change here. |
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.
Maybe update the PR description to have an overview of how proxysql is integrated before merging.
Add an upstream ProxySQL container to our docker-compose. Configure ProxySQL to manage database connections for our unit and integration tests.
Fixes #5873