chore: remove pgbouncer from AIO image except pg role [GEN-8039] #920
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.
Same changes as previous PR #907 , except this will keep the .sql that creates the pgbouncer role. This will be kept for now until the full pgbouncer cleanup happens, since there were migrations failing due to the lack of pgbouncer role present, when creating new projects in Fly, during tests in Staging.
Before opening the PR, this changes were tested with
aio-15.1.1.31-no-pgbouncer-docker
image in staging, which went through, creating a complete project with no issues and no pgbouncer presence, except for the role, as mentioned before.