-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add support for next_query_flagIN #74
Add support for next_query_flagIN #74
Conversation
With C(CASELESS) the match is case insensitive. With C(GLOBAL) the replace | ||
is global (replaces all matches and not just the first). | ||
For backward compatibility, only C(CASELESS) is the enabled by default. | ||
version_added: "2.9" |
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.
version added would be 1.3.0
.
can you also please add a changelog fragement @ls-michielrensen?
futhermore I'm afraid that this will break backwards compatibility with proxysql 1.x.x like #71 #73
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.
Yeah it probably is not backwards compatible no, do we need to add a version constraint somewhere?
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.
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.
link to the changelog related doc for convenience https://docs.ansible.com/ansible/latest/community/development_process.html#creating-a-changelog-fragment
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.
@ls-michielrensen thanks for the PR!
I'm abstain from evaluating this changes as I'm not a specialist.
@markuman knows better:)
I would also add:
Co-authored-by: Andrew Klychkov <aaklychkov@mail.ru>
Co-authored-by: Andrew Klychkov <aaklychkov@mail.ru>
Added the example from this PR description to the block
Uh gotta figure that out (first-timer here...) Changelog fragment added
Added version constraint as suggested by @markuman in ca47c32 |
@markuman Your suggestion to add version constraints seemed to have broken the Integration tests. I guess we'll have to figure that out some other way... |
No, there is something failing that is not affected by your PR
However, as mentioned above, you can revert it, because the table also exists in 1.4.15. It was my fault. |
I see two sanity erros locally
|
@markuman thanks, fixed the sanity failures, silly mistake on my end. Also reverted the version constraint 👍🏻 |
Integration test pass locally for |
@markuman thanks for double checking. Can you point me in the right direction as to how to run the integration tests locally? |
@Andersson007 thanks for the headsup, worked flawlessly 👍🏻 |
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.
LGTM
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.
LGTM from general perspective:)
@ls-michielrensen thanks for the contribution! @markuman thanks for reviewing and merging! |
@Andersson007 you're welcome, was a fun experience and quickly executed 👍🏻 |
SUMMARY
This PR adds support for
next_query_flagIN
in the proxysql_query_rules pluginISSUE TYPE
COMPONENT NAME
proxysql_query_rules
ADDITIONAL INFORMATION
next_query_flagIN
allows to chain query rules which is useful for when example you want to allow a SELECT after an INSERT/UPDATE/DELETE to run on the same hostgroup (avoiding replication lag).