-
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
Adding a ";" (semi-colon) as part of the value breaks the tools output #7
Comments
Hi @NathanaelA! If you can temporarily workaround it, could you link to this issue once you open the PR on pgbouncer? This way we have the full context and can reproduce your problem 🙂 |
The above CLI command I provided will show you the issue. Just run it and you should see the key value will have back ticks around it.... The only way to work around it currently that I'm using in my own replacement version of the
This is added as the last line in the |
I thought this issue was somewhat blocking the proposed PR for |
I pushed #9 with a cli flag to allow disabling the behavior by ignoring inline comments (which removes the special meaning of the semicolon). Could you check if that helps with your issue?
|
@pablogalegoc - Actually it was/is blocking a new PR for pgbouncer that I haven't finished. If this change fixes the ini issue, then I'll be putting a PR up for the |
@juamedgod - Is there a release/RC version of this with this change that I can test, or do I have to build it? |
You can grab it from the artifacts in the Circle CI run from the PR: Here is a direct link to the artifact: |
Hi all, I'm going to close this issue due to inactivity but feel free to send a contribution if are open to contribute any related feature. |
Trying to create a PR for the postgresql pgbouncer image of yours for the auth_query value I ran into this issue...
doing a
ini-file --section "section" -- key "key" --value "test;" ./test.ini
will create file that looks like:
it back-ticks the value, which seems to break some ini-parsers like the pgbouncer ini parser
I expected:
The text was updated successfully, but these errors were encountered: