-
Notifications
You must be signed in to change notification settings - Fork 940
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
Allow db extensions to be configured declaratively #490
Labels
Comments
This would be super useful |
We use a whitelist extension to allow non super users to install
extensions. This works well for us. Have a look in spilo.
But more ideas of what makes sense are welcome and this is not necessarily
an objection to the idea.
…On Fri 15. Feb 2019 at 16:21, Henri Cook ***@***.***> wrote:
This would be super useful
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#490 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABYGQ0oRLnLYv60iMpJU21bJ_nY0T5Uqks5vNtBrgaJpZM4a92T0>
.
|
Hm, is something missing?
|
@redbaron Can you check that you have |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Extensions are to be enabled per database and application normally cannot do it as it doesn't use superuser. What do you think about changing pg.spec.databases to following (can be done in a backward compatible way were old shape of this key is transformed into new one with empty
extensions
key):then operator checks for enabled extension in a reconciliation loop and enables missing ones.
With this change it would be fairly straightforward to start using new extension without manual intervention.
Alternative approach is to have a dedicated migration step in CI/CD pipeline which uses superuser to make all necessary adjustments, but this might be a bigger change for some setups (like ours) where application is responsible for it's own migrations at start time.
The text was updated successfully, but these errors were encountered: