feat: do not enable pgjwt by default in pg 15 #1592
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Comment on lines
37
to
43
| - name: Remove pgjwt from supautils.conf if 15 build | ||
| ansible.builtin.command: | ||
| cmd: > | ||
| sed -i 's/ pgjwt,//g' | ||
| /etc/postgresql-custom/supautils.conf | ||
| when: is_psql_15 and stage2_nix | ||
| become: yes |
There was a problem hiding this comment.
Q: Can this be tried locally?
If not, we're planning to remove ansible later right?
There was a problem hiding this comment.
@steve-chavez yes we are planning to remove ansible later. This can be tried locally, and will be part of our local testing env I'll add a change for that in this PR.
I am starting with the auth project to migrate package and config steps out of ansible. Then likely postgres will be next, fwiw.
…ed by supautils in all versions)
delgado3d
approved these changes
May 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Going forward we will not enable pgjwt by default in postgres 15.x